www-announce mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Bognar <jamesbog...@apache.org>
Subject [ANNOUNCEMENT] Apache Juneau 6.4.0 (incubating) Released
Date Thu, 05 Oct 2017 15:05:07 GMT
Hello all,

The Apache Juneau team is proud to announce the release of Juneau
6.4.0.incubating.

Apache Juneau is...

   - A universal toolkit for marshalling POJOs to a wide variety of content
   types using a common framework.
   - A universal REST server API for creating Swagger-based
   self-documenting REST interfaces using POJOs, simply deployed as one or
   more top-level servlets in any Servlet 3.1.0+ container.
   - A universal REST client API for interacting with Juneau or 3rd-party
   REST interfaces using POJOs and proxy interfaces.
   - A sophisticated configuration file API.
   - A REST microservice API that combines all the features above with a
   simple configurable Jetty server for creating lightweight standalone REST
   interfaces that start up in milliseconds.
   - Built on top of Servlet and Apache HttpClient APIs that allow you to
   use the newest HTTP/2 features such as request/response multiplexing and
   server push.

This release makes significant changes to the packaging of the artifacts.
We've also added lifecycle handlers to the REST APIs and make REST
microservice cofiguration considerably more flexible.

The release is available here (don't forget to verify the signatures):
http://juneau.incubator.apache.org/index.html#downloads.html

Release notes can be found here:
http://juneau.incubator.apache.org/site/apidocs/overview-summary.html#6.4.0

We welcome your help and feedback. For more information on the project and
how to get involved, visit the project website at
http://juneau.incubator.apache.org/

Disclaimer:
Apache Juneau is an effort undergoing incubation at The Apache Software
Foundation (ASF) sponsored by the Apache Incubator PMC. Incubation is
required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process have stabilized in a manner consistent with other successful ASF
projects. While incubation status is not necessarily a reflection
of the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.

Mime
View raw message