The Apache Pluto Community is proud to announce the first general availablility release of Apache Pluto - pluto 1.0.1. Pluto is the reference implementation of the Java Portlet Specification (JSR-168).
Pluto 1.0.1 contains fixes for nearly all reported bugs and supports hot deployment of Portlets through the Administrative tools provided with the Portal Driver.
Pluto 1.0.1 distributions can be accessed from: http://portals.apache.org/pluto/mirrors.cgi
The Apache Pluto Community is proud to announce the release of Apache Pluto 1.0.1-rc-2: the third binary release of the reference implementation of the Java Portlet Specification.
The third release candidate contains several bug fixes and will be followed by a general availability of Pluto 1.0.1. In addition to bug fixes, the release contains a new administrative portlet which can be used to deploy portlets.
The Apache Pluto Community is proud to announce the release of Apache Pluto 1.0.1-rc-2: the second binary release of the reference implementation of the Java Portlet Specification.
Community feedback will decide if a further release candidate is required before a final release.
The Java Portlet Specification defines a Portlet API very similar to the Servlet API. The API provides a means for aggregating disperate content sources. The specification addresses security and personalization considerations and defines a standard with which these sources, or portlets can be deployed.
Pluto is an embedable portlet container which will typically be bundled within a fully functional Portal. The Pluto community has developed a simple portal driver implementation which allows for the testing and development of portlets with the container. The Pluto testsuite is an implementation agnostic portlet application which tests several basic operations of the container in which it is deployed.
The distribution is organized into four releases:
The Apache Pluto Community is proud to announce the release of Apache Pluto 1.0.1-rc-1: the first binary release of the reference implementation of the Java Portlet Specification.
Pluto 1.0.1-rc-1 is considered a release candidate. The promotion of this release candidate to general availability is expected within the few weeks, pending feedback from the community.
The Java Portlet Specification defines a Portlet API very similar to the Servlet API. The API provides a means for aggregating disperate content sources. The specification addresses security and personalization considerations and defines a standard with which these sources, or portlets can be deployed.
Pluto is an embedable portlet container which will typically be bundled within a fully functional Portal. The Pluto community has developed a simple portal driver implementation which allows for the testing and development of portlets with the container. The Pluto testsuite is an implementation agnostic portlet application which tests several basic operations of the container in which it is deployed.
The distribution is organized into four releases:
The Pluto Team is currently working on the first public release which is expected by the end of September.
The Pluto Project is now a sub project under the portals PMC and has moved out of the incubator. This move comes with some changes regarding mailing addresses etc. In addition Pluto now uses Subversion instead of CVS.
As most projects in the ASF, we are superseding Bugzilla and using JIRA to manage project issues. New URL for Pluto issues.
The Pluto Community has finalized a declaration of intent which clarifies the direction with which Pluto development will move forward.
The maven subproject documentation is now being generated and included in the Pluto documentation builds.
Pluto is now managed by maven and it's website has subsequently recieved a face lift. http://jakarta.apache.org/pluto now contains additional information that should be helpfull in establishing this community.
Pluto has been added to Bugzilla (http://issues.apache.org/bugzilla). Issues, bugs, and enhancements will now be managed through this bug database.