You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-scm@portals.apache.org by es...@apache.org on 2007/03/20 00:46:41 UTC
svn commit: r520179 - in /portals/pluto/trunk/pluto-site/src/site/xdoc:
download.xml index.xml mission.xml news.xml powered.xml
Author: esm
Date: Mon Mar 19 16:46:40 2007
New Revision: 520179
URL: http://svn.apache.org/viewvc?view=rev&rev=520179
Log:
Updating line endings only.
Modified:
portals/pluto/trunk/pluto-site/src/site/xdoc/download.xml (contents, props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml (contents, props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/mission.xml (contents, props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/news.xml (contents, props changed)
portals/pluto/trunk/pluto-site/src/site/xdoc/powered.xml (contents, props changed)
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/download.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/download.xml?view=diff&rev=520179&r1=520178&r2=520179
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/download.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/download.xml Mon Mar 19 16:46:40 2007
@@ -1,46 +1,46 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-implied.
-
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-
-<document>
-
- <properties>
- <title>Apache Pluto Downloads</title>
- </properties>
-
- <body>
-
- <section name="Download Pluto">
- <p>
- The Apache Pluto source and binary distributions can be downloaded from
- <a href="http://www.apache.org/dyn/closer.cgi/portals/pluto/">a Pluto
- distribution mirror</a>.
- </p>
- </section>
-
- <section name="Browse Distribution Archives">
- <p>
- You can browse and download our distribution archive
- <a href="http://archive.apache.org/dist/portals/pluto/">from here</a>.
- </p>
- </section>
-
- </body>
-
-</document>
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<document>
+
+ <properties>
+ <title>Apache Pluto Downloads</title>
+ </properties>
+
+ <body>
+
+ <section name="Download Pluto">
+ <p>
+ The Apache Pluto source and binary distributions can be downloaded from
+ <a href="http://www.apache.org/dyn/closer.cgi/portals/pluto/">a Pluto
+ distribution mirror</a>.
+ </p>
+ </section>
+
+ <section name="Browse Distribution Archives">
+ <p>
+ You can browse and download our distribution archive
+ <a href="http://archive.apache.org/dist/portals/pluto/">from here</a>.
+ </p>
+ </section>
+
+ </body>
+
+</document>
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/download.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml?view=diff&rev=520179&r1=520178&r2=520179
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml Mon Mar 19 16:46:40 2007
@@ -1,132 +1,132 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
-Licensed to the Apache Software Foundation (ASF) under one or more
-contributor license agreements. See the NOTICE file distributed with
-this work for additional information regarding copyright ownership.
-The ASF licenses this file to You under the Apache License, Version 2.0
-(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-implied.
-
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-
-<document>
-
- <properties>
- <title>Welcome to Pluto</title>
- </properties>
-
- <body>
-
- <section name="Welcome to Pluto">
-
- <div class="highlightBox">
- <h5>JSR-286 - The Java Portlet API 2.0</h5>
- <p>
- The Java Portlet API version 2.0 specification is now under
- development by the JSR-286 Expert Group under the auspices of the
- <a href="http://www.jcp.org">Java Community Process</a>.
- Details on the specification work can be
- found at the <a href="http://jcp.org/en/jsr/detail?id=286">JSR-286 web
- site</a>. Drafts of the new portlet specification and API can
- be found at <a href="http://ipc658.inf-swt.uni-jena.de/spec/">http://ipc658.inf-swt.uni-jena.de/spec/</a>.
- The Expert Group is very interested in feedback from the
- community. Send your comments to <a href="mailto:jsr-286-comments@jcp.org">
- jsr-286-comments@jcp.org</a>.
- </p>
- </div>
-
- <div class="highlightBox">
- <h5>Get Pluto 1.1.0</h5>
- <p>
- <a href="http://www.apache.org/dyn/closer.cgi/portals/pluto/">
- <img valign="top" src="images/download.gif" border="0" title="download"/>
- Download
- </a>
- Pluto 1.1.0 GA (19Mb)
- </p>
- <ul>
- <li><a href="v11/getting-started.html">Installation Guide</a></li>
- </ul>
- </div>
-
- <p>
- Pluto is the Reference Implementation of the Java Portlet Specfication.
- The current version of this specification is JSR 168.
- </p>
- <p>
- Portlets are designed to run in the context of a portal. They are
- written to the Portlet API which are similar to the Servlet API.
- </p>
- <p>
- In contrast to servlets, portlets may not do things like sending
- redirects or errors to browsers directly, forwarding requests or writing
- arbitrary markup to the output stream to assure that they don?t distract
- the portal web application which uses them. Another difference compared
- to servlets is that portlets rely on portal specific infrastructure
- functions such as access to user profile information, standard interface
- for storing/retrieving persistent settings, getting client information,
- etc. Generally, portlets are administrated more dynamically than
- servlets typically are.
- </p>
- <p>
- A portlet container provides a runtime environment for portlets
- implemented according to the Portlet API. In this environment portlets
- can be instantiated, used and finally destroyed. The portlet container
- is not a stand-alone container like the servlet container; instead it is
- implemented as a thin layer on top of the servlet container and reuses
- the functionality provided by the servlet container.
- </p>
- <p>
- Pluto serves as portlet container that implements the Portlet API and
- offers developers a working example platform from which they can test
- their portlets. However, it's cumbersome to execute and test the portlet
- container without a driver, in this case, the portal. Pluto's simple
- portal component is built only on the portlet container's and the JSR
- 168's requirements. (In contrast, the more sophisticated, Jetspeed
- project concentrates on the portal itself rather than the portlet
- container, and considers requirements from other groups.)
- </p>
- </section>
-
- <section name="Project Status">
- <p>
- Apache Pluto is a subproject of the Apache Portals Project. The current
- stable release of Apache Pluto is version 1.1.0, which is currently being
- actively developed as the Reference Implementation of JSR-286.
- </p>
- <subsection name="Pluto 1.0.1">
- <p>
- Pluto 1.0.1 is the first stable release of Pluto. This version of
- Pluto is utilized as the portlet container for Jetspeed and other
- portals. In addition, Pluto 1.0.1 is embeded within Apache Geronimo.
- </p>
- </subsection>
- <subsection name="Pluto 1.1">
- <p>
- Pluto 1.1 introduces a new container architecture. If you are
- embedding Pluto in your portal, realize that 1.1 is not binarily
- compatible with Pluto 1.0.x.
- </p>
- <p>
- Pluto 1.1 aims to simplify the architecture in order to make it more
- user and developer friendly. You should find Pluto 1.1 easier to get
- started with, easier to understand, and easier to embed with your
- portal. Your feedback regarding how far we've come is always welcome
- on the user and developer mailing lists!
- </p>
- </subsection>
- </section>
-
- </body>
-
-</document>
-
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<document>
+
+ <properties>
+ <title>Welcome to Pluto</title>
+ </properties>
+
+ <body>
+
+ <section name="Welcome to Pluto">
+
+ <div class="highlightBox">
+ <h5>JSR-286 - The Java Portlet API 2.0</h5>
+ <p>
+ The Java Portlet API version 2.0 specification is now under
+ development by the JSR-286 Expert Group under the auspices of the
+ <a href="http://www.jcp.org">Java Community Process</a>.
+ Details on the specification work can be
+ found at the <a href="http://jcp.org/en/jsr/detail?id=286">JSR-286 web
+ site</a>. Drafts of the new portlet specification and API can
+ be found at <a href="http://ipc658.inf-swt.uni-jena.de/spec/">http://ipc658.inf-swt.uni-jena.de/spec/</a>.
+ The Expert Group is very interested in feedback from the
+ community. Send your comments to <a href="mailto:jsr-286-comments@jcp.org">
+ jsr-286-comments@jcp.org</a>.
+ </p>
+ </div>
+
+ <div class="highlightBox">
+ <h5>Get Pluto 1.1.0</h5>
+ <p>
+ <a href="http://www.apache.org/dyn/closer.cgi/portals/pluto/">
+ <img valign="top" src="images/download.gif" border="0" title="download"/>
+ Download
+ </a>
+ Pluto 1.1.0 GA (19Mb)
+ </p>
+ <ul>
+ <li><a href="v11/getting-started.html">Installation Guide</a></li>
+ </ul>
+ </div>
+
+ <p>
+ Pluto is the Reference Implementation of the Java Portlet Specfication.
+ The current version of this specification is JSR 168.
+ </p>
+ <p>
+ Portlets are designed to run in the context of a portal. They are
+ written to the Portlet API which are similar to the Servlet API.
+ </p>
+ <p>
+ In contrast to servlets, portlets may not do things like sending
+ redirects or errors to browsers directly, forwarding requests or writing
+ arbitrary markup to the output stream to assure that they don?t distract
+ the portal web application which uses them. Another difference compared
+ to servlets is that portlets rely on portal specific infrastructure
+ functions such as access to user profile information, standard interface
+ for storing/retrieving persistent settings, getting client information,
+ etc. Generally, portlets are administrated more dynamically than
+ servlets typically are.
+ </p>
+ <p>
+ A portlet container provides a runtime environment for portlets
+ implemented according to the Portlet API. In this environment portlets
+ can be instantiated, used and finally destroyed. The portlet container
+ is not a stand-alone container like the servlet container; instead it is
+ implemented as a thin layer on top of the servlet container and reuses
+ the functionality provided by the servlet container.
+ </p>
+ <p>
+ Pluto serves as portlet container that implements the Portlet API and
+ offers developers a working example platform from which they can test
+ their portlets. However, it's cumbersome to execute and test the portlet
+ container without a driver, in this case, the portal. Pluto's simple
+ portal component is built only on the portlet container's and the JSR
+ 168's requirements. (In contrast, the more sophisticated, Jetspeed
+ project concentrates on the portal itself rather than the portlet
+ container, and considers requirements from other groups.)
+ </p>
+ </section>
+
+ <section name="Project Status">
+ <p>
+ Apache Pluto is a subproject of the Apache Portals Project. The current
+ stable release of Apache Pluto is version 1.1.0, which is currently being
+ actively developed as the Reference Implementation of JSR-286.
+ </p>
+ <subsection name="Pluto 1.0.1">
+ <p>
+ Pluto 1.0.1 is the first stable release of Pluto. This version of
+ Pluto is utilized as the portlet container for Jetspeed and other
+ portals. In addition, Pluto 1.0.1 is embeded within Apache Geronimo.
+ </p>
+ </subsection>
+ <subsection name="Pluto 1.1">
+ <p>
+ Pluto 1.1 introduces a new container architecture. If you are
+ embedding Pluto in your portal, realize that 1.1 is not binarily
+ compatible with Pluto 1.0.x.
+ </p>
+ <p>
+ Pluto 1.1 aims to simplify the architecture in order to make it more
+ user and developer friendly. You should find Pluto 1.1 easier to get
+ started with, easier to understand, and easier to embed with your
+ portal. Your feedback regarding how far we've come is always welcome
+ on the user and developer mailing lists!
+ </p>
+ </subsection>
+ </section>
+
+ </body>
+
+</document>
+
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/index.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/mission.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/mission.xml?view=diff&rev=520179&r1=520178&r2=520179
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/mission.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/mission.xml Mon Mar 19 16:46:40 2007
@@ -1,84 +1,84 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-implied.
-
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-
-<document>
-
- <properties>
- <title>The Pluto Project Mission</title>
- </properties>
-
- <body>
- <section name="The Pluto Project Mission">
- <p>
- The Pluto Portlet Container is the Reference Implementation of the Java
- Portlet Specification. As such, Pluto offers the development community
- a reference for interpretation of the specification, portlet developers
- a container with which compliant portlets can be tested, and portal
- developers a compliant container with which they can integrate.
- </p>
- <p>
- The following document attempts to clarify the development priorities
- of the Apache Pluto project.
- </p>
- <p>
- The primary concern of the pluto community is to ensure that the Pluto
- Container maintains compatibility with the most current Java Portlet
- Specification. Enhancements and bug fixes should be completed in a
- manner in which compatibility is maintained.
- </p>
- <p>
- It is the responsibility of the pluto development team to ensure that
- no ambiguity is introduced into the reference implementation. No
- enhancements should be implemented which introduce questions about the
- specification.
- </p>
- <p>
- It is desirable for Pluto to become a robust and easy to use portlet
- container. This will facilitate its wider acceptance and usage in the
- community. In order to accomplish these goals, it is assumed that
- enhancements which are above and beyond the specification will be
- introduced. These enhancements may be integrated with Pluto as long as
- they do not compromise the integrity of the reference implementation as
- described above.
- </p>
- <p>
- Furthermore, functionality which is clearly beyond the scope of the
- specification should be documented as such and placed into a package
- which helps to distinguish it as such. The Pluto container should
- always remain fully specification compliant and in working state when
- these enhancements are removed. In most cases, this removal should be
- supported through configuration parameters.
- </p>
- <p>
- Finally, while the pluto project contains several subprojects, it is
- important to realize that the container itself is the most important
- aspect of the project. It, in an of itself, is the Java Portlet
- reference implementation. The portal driver (Pluto Test Portal),
- testsuite, and deployer exist to simplfy the use and testing of the
- container. As such, any significant enhancements to these components
- (most especially the portal driver) should be scrutinized before
- implementation, as most likely, it is outside the scope of the pluto
- project and belong in a portal full implementation.
- </p>
- </section>
- </body>
-
-</document>
-
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<document>
+
+ <properties>
+ <title>The Pluto Project Mission</title>
+ </properties>
+
+ <body>
+ <section name="The Pluto Project Mission">
+ <p>
+ The Pluto Portlet Container is the Reference Implementation of the Java
+ Portlet Specification. As such, Pluto offers the development community
+ a reference for interpretation of the specification, portlet developers
+ a container with which compliant portlets can be tested, and portal
+ developers a compliant container with which they can integrate.
+ </p>
+ <p>
+ The following document attempts to clarify the development priorities
+ of the Apache Pluto project.
+ </p>
+ <p>
+ The primary concern of the pluto community is to ensure that the Pluto
+ Container maintains compatibility with the most current Java Portlet
+ Specification. Enhancements and bug fixes should be completed in a
+ manner in which compatibility is maintained.
+ </p>
+ <p>
+ It is the responsibility of the pluto development team to ensure that
+ no ambiguity is introduced into the reference implementation. No
+ enhancements should be implemented which introduce questions about the
+ specification.
+ </p>
+ <p>
+ It is desirable for Pluto to become a robust and easy to use portlet
+ container. This will facilitate its wider acceptance and usage in the
+ community. In order to accomplish these goals, it is assumed that
+ enhancements which are above and beyond the specification will be
+ introduced. These enhancements may be integrated with Pluto as long as
+ they do not compromise the integrity of the reference implementation as
+ described above.
+ </p>
+ <p>
+ Furthermore, functionality which is clearly beyond the scope of the
+ specification should be documented as such and placed into a package
+ which helps to distinguish it as such. The Pluto container should
+ always remain fully specification compliant and in working state when
+ these enhancements are removed. In most cases, this removal should be
+ supported through configuration parameters.
+ </p>
+ <p>
+ Finally, while the pluto project contains several subprojects, it is
+ important to realize that the container itself is the most important
+ aspect of the project. It, in an of itself, is the Java Portlet
+ reference implementation. The portal driver (Pluto Test Portal),
+ testsuite, and deployer exist to simplfy the use and testing of the
+ container. As such, any significant enhancements to these components
+ (most especially the portal driver) should be scrutinized before
+ implementation, as most likely, it is outside the scope of the pluto
+ project and belong in a portal full implementation.
+ </p>
+ </section>
+ </body>
+
+</document>
+
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/mission.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/news.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/news.xml?view=diff&rev=520179&r1=520178&r2=520179
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/news.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/news.xml Mon Mar 19 16:46:40 2007
@@ -1,212 +1,212 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<!--
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-implied.
-
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-
-<document>
-
- <properties>
- <title>Pluto Project News and Status</title>
- </properties>
-
- <body>
-
- <section name="News and Status">
-
- <h4>26 February 2007 - Portals Pluto 1.1.0 released</h4>
- <p>
- The Apache Pluto project is proud to announce the General Availability release of Pluto 1.1.0.
- This is the first GA release of the 1.1 line of Pluto, which is a major refactoring of Pluto 1.0.1
- to allow for easier integration of Pluto's portlet container into a portal and easier
- configuration of the Pluto portal driver, a bare-bones portal included with Pluto.
- </p>
- <p>
- This release fixes a number of outstanding bugs in Pluto 1.1. The bundled binary release, which
- has been updated to use Tomcat 5.5.20, now contains an administrative portlet for registering
- custom portlets in Pluto, which is linked to Tomcat's native war deployer.
- </p>
- <p>
- Pluto is the reference implementation of the JSR-168 (Portlet 1.0) specification for a portlet container.
- Pluto 1.1 is the basis for the reference implementation of the JSR-286 (Portlet 2.0) specification
- now under development by the JSR-286 Expert Group.
- </p>
-
-
-
- <h4>12 October 2006 - Portals Pluto 1.1.0 beta2 released</h4>
- <p>
- The Apache Pluto project is proud to announce the release of Pluto 1.1.0 beta2.
- This is the second release of the 1.1 version of Pluto, which is a major refactoring of Pluto 1.0.1
- to allow for easier integration of Pluto's portlet container into a portal and easier
- configuration of the Pluto portal driver, a bare-bones portal included with Pluto.
- </p>
- <p>
- This release fixes a number of bugs in Pluto 1.1 including ones that prevented standard portlet modes and
- window states from functioning properly. We've also updated the binary release to deploy Pluto into
- Tomcat 5.5.17.
- </p>
- <p>
- Pluto is the reference implementation of the JSR-168 (Portlet 1.0) specification for a portlet container.
- Pluto 1.1 is the basis for the reference implementation of the JSR-286 (Portlet 2.0) specification
- now under development by the JSR-286 Expert Group.
- </p>
-
-
- <h4>1 June 2006 - Portals Pluto 1.1.0 beta1 released</h4>
- <p>
- The Apache Pluto project is proud to announce the release of Pluto 1.1.0 beta1.
- This is the first release of the 1.1 version of Pluto, which is a major refactoring of Pluto 1.0.1.
- This refactoring allows for easier integration of Pluto's portlet container into a portal and easier
- configuration of the Pluto portal driver, a bare-bones portal included with Pluto.
- </p>
- <p>
- Pluto is the reference implementation of the JSR-168 (Portlet 1.0) specification for a portlet container.
- Pluto 1.1 will be the basis for the reference implementation of the JSR-286 (Portlet 2.0) specification
- now under development by the JSR-286 Expert Group.
- </p>
-
- <h4>18 September 2005 - Portals Pluto 1.0.1 General Availability Released</h4>
- <p>
- The Apache Pluto Community is proud to announce the General
- Availablility release of Pluto 1.0.1, the reference implementation of
- the Java Portlet Specification (JSR-168).
- </p>
- <p>
- Nearly all the outstanding bugs have been fixed in this release.
- In addition, the Admin Portlet Application now supports hot deployment
- of custom portlets.
- </p>
-
- <h4>24 July 2005 - Portals Pluto 1.0.1-rc4 Released</h4>
-
- <h4>11 July 2005 - Portals Pluto 1.0.1-rc3 Released</h4>
- <p>
- 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.
- </p>
- <p>
- 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.
- </p>
-
- <h4>22 December 2004 - Portals Pluto 1.0.1-rc2 Released</h4>
- <p>
- 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.
- </p>
- <p>
- Community feedback will decide if a further release candidate is
- required before a final release.
- </p>
-
- <h4>8 October 2004 - Portals Pluto 1.0.1-rc1 Released</h4>
- <p>
- 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.
- </p>
- <p>
- 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.
- </p>
- <p>
- 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.
- </p>
- <p>
- 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.
- </p>
- <p>
- The distribution is organized into four releases:
- <ul>
- <li>A binary distribution bundled with Tomcat. This distribution is
- the easiest to install.</li>
- <li>A source distribution.</li>
- <li>A binary distribution containing the container library.</li>
- <li>A binary tools distribution with the portal driver and testsuite.</li>
- </ul>
- </p>
-
- <h4>September 2004 - Releasing Pluto</h4>
- <p>
- The Pluto Team is currently working on the first public release which
- is expected by the end of September.
- </p>
-
- <h4>July/August 2004 - Pluto moved out of the Incubator</h4>
- <p>
- 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.
- </p>
-
- <h4>May 2004 - Pluto moved issues to JIRA</h4>
- <p>
- As most projects in the ASF, we are superseding Bugzilla and using JIRA
- to manage project issues. New URL for
- <a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10560">
- Pluto issues</a>.
- </p>
-
- <h4>21 March 2004 - Pluto Declaration of Intent Finalized</h4>
- <p>
- The Pluto Community has finalized a declaration of intent which
- clarifies the direction with which Pluto development will move forward.
- </p>
-
- <h4>27 February 2004 - Pluto SubProject Documentation Available</h4>
- <p>
- The maven subproject documentation is now being generated and included
- in the Pluto documentation builds.
- </p>
-
- <h4>10 November 2003 - Pluto Gets a Face Lift</h4>
- <p>
- 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.
- </p>
-
- <h4>9 November 2003 - Pluto added to Bugzilla</h4>
- <p>
- Pluto has been added to Bugzilla
- (<a href="http://issues.apache.org/bugzilla">http://issues.apache.org/bugzilla</a>).
- Issues, bugs, and enhancements will now be managed through this bug
- database.
- </p>
-
- </section>
-
- </body>
-
-</document>
-
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+
+<document>
+
+ <properties>
+ <title>Pluto Project News and Status</title>
+ </properties>
+
+ <body>
+
+ <section name="News and Status">
+
+ <h4>26 February 2007 - Portals Pluto 1.1.0 released</h4>
+ <p>
+ The Apache Pluto project is proud to announce the General Availability release of Pluto 1.1.0.
+ This is the first GA release of the 1.1 line of Pluto, which is a major refactoring of Pluto 1.0.1
+ to allow for easier integration of Pluto's portlet container into a portal and easier
+ configuration of the Pluto portal driver, a bare-bones portal included with Pluto.
+ </p>
+ <p>
+ This release fixes a number of outstanding bugs in Pluto 1.1. The bundled binary release, which
+ has been updated to use Tomcat 5.5.20, now contains an administrative portlet for registering
+ custom portlets in Pluto, which is linked to Tomcat's native war deployer.
+ </p>
+ <p>
+ Pluto is the reference implementation of the JSR-168 (Portlet 1.0) specification for a portlet container.
+ Pluto 1.1 is the basis for the reference implementation of the JSR-286 (Portlet 2.0) specification
+ now under development by the JSR-286 Expert Group.
+ </p>
+
+
+
+ <h4>12 October 2006 - Portals Pluto 1.1.0 beta2 released</h4>
+ <p>
+ The Apache Pluto project is proud to announce the release of Pluto 1.1.0 beta2.
+ This is the second release of the 1.1 version of Pluto, which is a major refactoring of Pluto 1.0.1
+ to allow for easier integration of Pluto's portlet container into a portal and easier
+ configuration of the Pluto portal driver, a bare-bones portal included with Pluto.
+ </p>
+ <p>
+ This release fixes a number of bugs in Pluto 1.1 including ones that prevented standard portlet modes and
+ window states from functioning properly. We've also updated the binary release to deploy Pluto into
+ Tomcat 5.5.17.
+ </p>
+ <p>
+ Pluto is the reference implementation of the JSR-168 (Portlet 1.0) specification for a portlet container.
+ Pluto 1.1 is the basis for the reference implementation of the JSR-286 (Portlet 2.0) specification
+ now under development by the JSR-286 Expert Group.
+ </p>
+
+
+ <h4>1 June 2006 - Portals Pluto 1.1.0 beta1 released</h4>
+ <p>
+ The Apache Pluto project is proud to announce the release of Pluto 1.1.0 beta1.
+ This is the first release of the 1.1 version of Pluto, which is a major refactoring of Pluto 1.0.1.
+ This refactoring allows for easier integration of Pluto's portlet container into a portal and easier
+ configuration of the Pluto portal driver, a bare-bones portal included with Pluto.
+ </p>
+ <p>
+ Pluto is the reference implementation of the JSR-168 (Portlet 1.0) specification for a portlet container.
+ Pluto 1.1 will be the basis for the reference implementation of the JSR-286 (Portlet 2.0) specification
+ now under development by the JSR-286 Expert Group.
+ </p>
+
+ <h4>18 September 2005 - Portals Pluto 1.0.1 General Availability Released</h4>
+ <p>
+ The Apache Pluto Community is proud to announce the General
+ Availablility release of Pluto 1.0.1, the reference implementation of
+ the Java Portlet Specification (JSR-168).
+ </p>
+ <p>
+ Nearly all the outstanding bugs have been fixed in this release.
+ In addition, the Admin Portlet Application now supports hot deployment
+ of custom portlets.
+ </p>
+
+ <h4>24 July 2005 - Portals Pluto 1.0.1-rc4 Released</h4>
+
+ <h4>11 July 2005 - Portals Pluto 1.0.1-rc3 Released</h4>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+
+ <h4>22 December 2004 - Portals Pluto 1.0.1-rc2 Released</h4>
+ <p>
+ 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.
+ </p>
+ <p>
+ Community feedback will decide if a further release candidate is
+ required before a final release.
+ </p>
+
+ <h4>8 October 2004 - Portals Pluto 1.0.1-rc1 Released</h4>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ 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.
+ </p>
+ <p>
+ The distribution is organized into four releases:
+ <ul>
+ <li>A binary distribution bundled with Tomcat. This distribution is
+ the easiest to install.</li>
+ <li>A source distribution.</li>
+ <li>A binary distribution containing the container library.</li>
+ <li>A binary tools distribution with the portal driver and testsuite.</li>
+ </ul>
+ </p>
+
+ <h4>September 2004 - Releasing Pluto</h4>
+ <p>
+ The Pluto Team is currently working on the first public release which
+ is expected by the end of September.
+ </p>
+
+ <h4>July/August 2004 - Pluto moved out of the Incubator</h4>
+ <p>
+ 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.
+ </p>
+
+ <h4>May 2004 - Pluto moved issues to JIRA</h4>
+ <p>
+ As most projects in the ASF, we are superseding Bugzilla and using JIRA
+ to manage project issues. New URL for
+ <a href="http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10560">
+ Pluto issues</a>.
+ </p>
+
+ <h4>21 March 2004 - Pluto Declaration of Intent Finalized</h4>
+ <p>
+ The Pluto Community has finalized a declaration of intent which
+ clarifies the direction with which Pluto development will move forward.
+ </p>
+
+ <h4>27 February 2004 - Pluto SubProject Documentation Available</h4>
+ <p>
+ The maven subproject documentation is now being generated and included
+ in the Pluto documentation builds.
+ </p>
+
+ <h4>10 November 2003 - Pluto Gets a Face Lift</h4>
+ <p>
+ 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.
+ </p>
+
+ <h4>9 November 2003 - Pluto added to Bugzilla</h4>
+ <p>
+ Pluto has been added to Bugzilla
+ (<a href="http://issues.apache.org/bugzilla">http://issues.apache.org/bugzilla</a>).
+ Issues, bugs, and enhancements will now be managed through this bug
+ database.
+ </p>
+
+ </section>
+
+ </body>
+
+</document>
+
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/news.xml
------------------------------------------------------------------------------
svn:eol-style = native
Modified: portals/pluto/trunk/pluto-site/src/site/xdoc/powered.xml
URL: http://svn.apache.org/viewvc/portals/pluto/trunk/pluto-site/src/site/xdoc/powered.xml?view=diff&rev=520179&r1=520178&r2=520179
==============================================================================
--- portals/pluto/trunk/pluto-site/src/site/xdoc/powered.xml (original)
+++ portals/pluto/trunk/pluto-site/src/site/xdoc/powered.xml Mon Mar 19 16:46:40 2007
@@ -1,89 +1,89 @@
-<?xml version="1.0"?>
-<!--
+<?xml version="1.0"?>
+<!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the "License"); you may not use this file except in compliance with
-the License. You may obtain a copy of the License at
-
-http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-implied.
-
-See the License for the specific language governing permissions and
-limitations under the License.
--->
-<document>
- <properties>
- <title>Pluto Project | Declaration of Intent</title>
- </properties>
-
-<body>
- <section name="Portal using Pluto">
- <p>
- The following portals use Pluto for their portlet container:
- <table>
- <tr><th>Portal</th><th>Website</th><th>License</th><th>Status</th><th>Pluto Version</th></tr>
- <tr><td>uPortal 3</td>
- <td><a href="http://www.uportal.org">http://www.uportal.org</a></td>
- <td>JA-SIG</td>
- <td></td>
- <td>1.1.x</td></tr>
- <tr><td>Sakai</td>
- <td><a href="http://www.sakaiproject.org">http://www.sakaiproject.org</a></td>
- <td>Sakai Foundation</td>
- <td></td>
- <td>1.1.x</td></tr>
- <tr><td>Apache Jetspeed 2</td>
- <td><a href="http://portals.apache.org/jetspeed-2">http://portals.apache.org/jetspeed-2</a></td>
- <td>Apache 2.0</td>
- <td></td>
- <td>1.0.1</td></tr>
- <tr><td>Apache Cocoon</td>
- <td><a href="http://cocoon.apache.org">http://cocoon.apache.org</a></td>
- <td>Apache 2.0</td>
- <td></td>
- <td>1.0.1</td></tr>
- <tr><td>uPortal 2</td>
- <td><a href="http://www.uportal.org">http://www.uportal.org</a></td>
- <td>JA-SIG</td>
- <td></td>
- <td>1.0.1</td></tr>
- <tr><td>InfoGlue</td>
- <td><a href="http://www.infoglue.org">http://www.infoglue.org</a></td>
- <td>GPL</td>
- <td></td>
- <td>1.0.1</td></tr>
- <tr><td>Jahia</td>
- <td><a href="http://www.jahia.org">http://www.jahia.org</a></td>
- <td><a href="http://www.collaborativesource.org">Proprietary</a></td>
- <td>(http://www.jahia.org/cvs), branch JAHIA_PLUTO_BRANCH</td>
- <td>1.0.1</td></tr>
- </table>
- </p>
-
- <p>
- The following applications utilize Pluto for providing Plugin Extensibility:
- <table>
- <tr><th>Portal</th><th>Website</th><th>License</th><th>Status</th><th>Pluto Version</th></tr>
- <tr><td>Apache Geronimo </td>
- <td><a href="http://geronimo.apache.org/">http://geronimo.apache.org</a></td>
- <td>Apache 2.0</td>
- <td>Web Management Console</td>
- <td>1.0.1</td></tr>
- <tr><td>Java Studio Creator 2.0</td>
- <td><a href="http://developers.sun.com/prodtech/javatools/jscreator/">http://developers.sun.com/prodtech/javatools/jscreator/</a></td>
- <td>Sun Microsystems Inc.</td>
- <td>Development Portal Server</td>
- <td>1.0.1</td></tr>
- </table>
- </p>
- </section>
-</body>
-</document>
-
-
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied.
+
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<document>
+ <properties>
+ <title>Pluto Project | Declaration of Intent</title>
+ </properties>
+
+<body>
+ <section name="Portal using Pluto">
+ <p>
+ The following portals use Pluto for their portlet container:
+ <table>
+ <tr><th>Portal</th><th>Website</th><th>License</th><th>Status</th><th>Pluto Version</th></tr>
+ <tr><td>uPortal 3</td>
+ <td><a href="http://www.uportal.org">http://www.uportal.org</a></td>
+ <td>JA-SIG</td>
+ <td></td>
+ <td>1.1.x</td></tr>
+ <tr><td>Sakai</td>
+ <td><a href="http://www.sakaiproject.org">http://www.sakaiproject.org</a></td>
+ <td>Sakai Foundation</td>
+ <td></td>
+ <td>1.1.x</td></tr>
+ <tr><td>Apache Jetspeed 2</td>
+ <td><a href="http://portals.apache.org/jetspeed-2">http://portals.apache.org/jetspeed-2</a></td>
+ <td>Apache 2.0</td>
+ <td></td>
+ <td>1.0.1</td></tr>
+ <tr><td>Apache Cocoon</td>
+ <td><a href="http://cocoon.apache.org">http://cocoon.apache.org</a></td>
+ <td>Apache 2.0</td>
+ <td></td>
+ <td>1.0.1</td></tr>
+ <tr><td>uPortal 2</td>
+ <td><a href="http://www.uportal.org">http://www.uportal.org</a></td>
+ <td>JA-SIG</td>
+ <td></td>
+ <td>1.0.1</td></tr>
+ <tr><td>InfoGlue</td>
+ <td><a href="http://www.infoglue.org">http://www.infoglue.org</a></td>
+ <td>GPL</td>
+ <td></td>
+ <td>1.0.1</td></tr>
+ <tr><td>Jahia</td>
+ <td><a href="http://www.jahia.org">http://www.jahia.org</a></td>
+ <td><a href="http://www.collaborativesource.org">Proprietary</a></td>
+ <td>(http://www.jahia.org/cvs), branch JAHIA_PLUTO_BRANCH</td>
+ <td>1.0.1</td></tr>
+ </table>
+ </p>
+
+ <p>
+ The following applications utilize Pluto for providing Plugin Extensibility:
+ <table>
+ <tr><th>Portal</th><th>Website</th><th>License</th><th>Status</th><th>Pluto Version</th></tr>
+ <tr><td>Apache Geronimo </td>
+ <td><a href="http://geronimo.apache.org/">http://geronimo.apache.org</a></td>
+ <td>Apache 2.0</td>
+ <td>Web Management Console</td>
+ <td>1.0.1</td></tr>
+ <tr><td>Java Studio Creator 2.0</td>
+ <td><a href="http://developers.sun.com/prodtech/javatools/jscreator/">http://developers.sun.com/prodtech/javatools/jscreator/</a></td>
+ <td>Sun Microsystems Inc.</td>
+ <td>Development Portal Server</td>
+ <td>1.0.1</td></tr>
+ </table>
+ </p>
+ </section>
+</body>
+</document>
+
+
Propchange: portals/pluto/trunk/pluto-site/src/site/xdoc/powered.xml
------------------------------------------------------------------------------
svn:eol-style = native