You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@portals.apache.org by ms...@apache.org on 2017/01/13 11:55:02 UTC
svn commit: r1778563 [1/4] - in /portals/site-live/pluto: ./ subprojects/
v101/ v11/ v20/ v30/
Author: msnicklous
Date: Fri Jan 13 11:55:02 2017
New Revision: 1778563
URL: http://svn.apache.org/viewvc?rev=1778563&view=rev
Log:
Updated pluto site for version 3.0.0
Modified:
portals/site-live/pluto/architecture.html
portals/site-live/pluto/download.html
portals/site-live/pluto/faq.html
portals/site-live/pluto/helping.html
portals/site-live/pluto/index.html
portals/site-live/pluto/issue-tracking.html
portals/site-live/pluto/license.html
portals/site-live/pluto/mail-lists.html
portals/site-live/pluto/mission.html
portals/site-live/pluto/news.html
portals/site-live/pluto/project-summary.html
portals/site-live/pluto/resources.html
portals/site-live/pluto/source-repository.html
portals/site-live/pluto/status.html
portals/site-live/pluto/subprojects/anttasks.html
portals/site-live/pluto/subprojects/container-api.html
portals/site-live/pluto/subprojects/driver.html
portals/site-live/pluto/subprojects/installer.html
portals/site-live/pluto/subprojects/portal.html
portals/site-live/pluto/subprojects/portlet-container.html
portals/site-live/pluto/subprojects/skin.html
portals/site-live/pluto/subprojects/subprojects.html
portals/site-live/pluto/subprojects/tag-library.html
portals/site-live/pluto/subprojects/testsuite.html
portals/site-live/pluto/subprojects/utilities.html
portals/site-live/pluto/team-list.html
portals/site-live/pluto/v101/install.html
portals/site-live/pluto/v101/resources.html
portals/site-live/pluto/v11/deploying.html
portals/site-live/pluto/v11/getting-started.html
portals/site-live/pluto/v11/release-notes.html
portals/site-live/pluto/v20/app-servers.html
portals/site-live/pluto/v20/deploying.html
portals/site-live/pluto/v20/embedding.html
portals/site-live/pluto/v20/getting-started.html
portals/site-live/pluto/v20/powered.html
portals/site-live/pluto/v20/release-notes-2.0.0.html
portals/site-live/pluto/v20/release-notes-2.0.1.html
portals/site-live/pluto/v20/release-notes-2.0.2.html
portals/site-live/pluto/v20/release-notes.html
portals/site-live/pluto/v30/deploying.html
portals/site-live/pluto/v30/getting-started.html
portals/site-live/pluto/v30/portlet-api.html
portals/site-live/pluto/v30/release-notes.html
portals/site-live/pluto/v30/tck.html
portals/site-live/pluto/v30/v3Features.html
Modified: portals/site-live/pluto/architecture.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/architecture.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/architecture.html (original)
+++ portals/site-live/pluto/architecture.html Fri Jan 13 11:55:02 2017
@@ -47,7 +47,7 @@
<div class="xleft">
- Last Published: 2016-12-02
+ Last Published: 2017-01-13
|
<a href="http://portals.apache.org/pluto" class="externalLink">Home</a>
</div>
@@ -251,19 +251,19 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section"><h2><a name="Pluto_Architecture"></a>Pluto Architecture</h2>
-<p><p>
-Portlets are run inside a portlet container (Pluto). This container provides the portlet with the
-required runtime environment. The portlet container manages the life cycle of all the portlets and provides
-interfaces for portlets to call into. The container also invokes methods on portlets targeted by an end-user
-interaction with the portal page. The portlet container passes on requests from the portal to the hosted portlets. The portlet container
-does not aggregate the content produced by the portlets; that is the portal’s job.
+<p><p>
+Portlets are run inside a portlet container (Pluto). This container provides the portlet with the
+required runtime environment. The portlet container manages the life cycle of all the portlets and provides
+interfaces for portlets to call into. The container also invokes methods on portlets targeted by an end-user
+interaction with the portal page. The portlet container passes on requests from the portal to the hosted portlets. The portlet container
+does not aggregate the content produced by the portlets; that is the portal’s job.
</p>
</p>
-<p>
- The following diagram depicts the architectural components of Pluto 2.0. Notice that the Portlet Container, Pluto, is embedded inside a Portal. Then
- cross-context (across web applications) request dispatches are made to render the portlet contents, as portlets will normally reside in a different applications
- from the portal and container. Depending on the implementation, often a PortletServlet is required, as shown below, in the class loader of the portlet application.
- This servlet is actually a part of the Pluto container implementation.
+<p>
+ The following diagram depicts the architectural components of Pluto 2.0. Notice that the Portlet Container, Pluto, is embedded inside a Portal. Then
+ cross-context (across web applications) request dispatches are made to render the portlet contents, as portlets will normally reside in a different applications
+ from the portal and container. Depending on the implementation, often a PortletServlet is required, as shown below, in the class loader of the portlet application.
+ This servlet is actually a part of the Pluto container implementation.
<img src="images/architecture.png" /></p>
</div>
@@ -274,7 +274,7 @@ does not aggregate the content produced
</div>
<div id="footer">
<div class="xright">©
- 2004-2016
+ 2004-2017
Apache Software Foundation
Modified: portals/site-live/pluto/download.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/download.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/download.html (original)
+++ portals/site-live/pluto/download.html Fri Jan 13 11:55:02 2017
@@ -47,7 +47,7 @@
<div class="xleft">
- Last Published: 2016-12-02
+ Last Published: 2017-01-13
|
<a href="http://portals.apache.org/pluto" class="externalLink">Home</a>
</div>
@@ -252,26 +252,26 @@
<div id="contentBox">
<div class="section"><h2><a name="Download_Pluto"></a>Download Pluto</h2>
<div class="highlightBox"><h4>About Pluto Distributions</h4>
-<p>
- There are a number of distributions to choose from depending
- on your needs.
- <ul><li><strong>pluto-bundle</strong> - Provides Pluto and Tomcat bundled together.
- If you are getting started with Pluto, this is the distribution you
+<p>
+ There are a number of distributions to choose from depending
+ on your needs.
+ <ul><li><strong>pluto-bundle</strong> - Provides Pluto and Tomcat bundled together.
+ If you are getting started with Pluto, this is the distribution you
want.</li>
-<li><strong>pluto-source-release</strong> - Provides the Pluto source code; requires
+<li><strong>pluto-source-release</strong> - Provides the Pluto source code; requires
that you build and deploy Pluto on your own.</li>
</ul>
</p>
-</div><p>
- The latest 2.0.3 version of Apache Pluto source and binary distributions can be downloaded from
- <a class="externalLink" href="http://www.apache.org/dyn/closer.cgi/portals/pluto/">a Pluto
- distribution mirror</a>.
+</div><p>
+ The latest 3.0.0 version of Apache Pluto source and binary distributions can be downloaded from
+ <a href="http://www.apache.org/dyn/closer.cgi/portals/pluto/" class="externalLink">a Pluto
+ distribution mirror</a>.
</p>
</div>
<div class="section"><h2><a name="Browse_Distribution_Archives"></a>Browse Distribution Archives</h2>
-<p>
- You can browse and download our distribution archive
- <a class="externalLink" href="http://archive.apache.org/dist/portals/pluto/">from here</a>.
+<p>
+ You can browse and download our distribution archive
+ <a href="http://archive.apache.org/dist/portals/pluto/" class="externalLink">from here</a>.
</p>
</div>
@@ -282,7 +282,7 @@
</div>
<div id="footer">
<div class="xright">©
- 2004-2016
+ 2004-2017
Apache Software Foundation
Modified: portals/site-live/pluto/faq.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/faq.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/faq.html (original)
+++ portals/site-live/pluto/faq.html Fri Jan 13 11:55:02 2017
@@ -47,7 +47,7 @@
<div class="xleft">
- Last Published: 2016-12-02
+ Last Published: 2017-01-13
|
<a href="http://portals.apache.org/pluto" class="externalLink">Home</a>
</div>
@@ -257,165 +257,164 @@
<li><a href="#portal">Is Pluto an Enterprise Portal?</a></li>
<li><a href="#simple-embed">What's the easiest way to include a portlet in my webapp (applies to Pluto 1.x only)</a></li>
<li><a href="#encoding">How can I change the default encoding of the Pluto Portal</a></li>
-<li><a href="#xml-parsing">
- Do I need to have xml parsers in an endorsed classloader? (e.g.in
- Tomcat's 5.5 common/endorsed directory)
+<li><a href="#xml-parsing">
+ Do I need to have xml parsers in an endorsed classloader? (e.g.in
+ Tomcat's 5.5 common/endorsed directory)
</a></li>
</ol>
</div>
<dl><dt><a name="version">Which version of Pluto 3.0 should I use?</a></dt>
-<dd>
- <p>
- Development for version 3.0 is nearly complete, but we don't have an official
- release available yet. We hope to have it available in December 2016.
- If you want to get started now, please see the Pluto 3.0
- <a href="./v30/getting-started.html">Getting Started</a> section for information on cloning
- the Pluto repository, building the portal, and learning from the version 3.0 sample portlets.
- </p>
- <p>
- All Pluto 2.x and 1.x versions are no longer active and only maintained for bug fixes.
- </p>
+<dd>
+ <p>
+ Version 3.0.0 is the latest stable release available from the download site.
+ If you want to build the current development version, please see the Pluto 3.0
+ <a href="./v30/getting-started.html">Getting Started</a> section for information on cloning
+ the Pluto repository, building the portal, and learning from the version 3.0 sample portlets.
+ </p>
+ <p>
+ All Pluto 2.x and 1.x versions are no longer active and only maintained for bug fixes.
+ </p>
<table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
</dd>
<dt><a name="version2.0">Which version of Pluto 2.0 should I use?</a></dt>
-<dd>
- <p>
- The latest release from the 2.0 series (2.0.3) is the current
- stable release. We recommend that you use this if you
- are looking for a stable release. 2.0 implements JSR 286 Java Portlet Specification 2.0 and requires Java 5 as minimum.
- </p>
- <p>
- All Pluto 1.x versions are no longer active and only maintained for bug fixes.
- </p>
+<dd>
+ <p>
+ The latest release from the 2.0 series (2.0.3) is the current
+ stable release. We recommend that you use this if you
+ are looking for a stable release. 2.0 implements JSR 286 Java Portlet Specification 2.0 and requires Java 5 as minimum.
+ </p>
+ <p>
+ All Pluto 1.x versions are no longer active and only maintained for bug fixes.
+ </p>
<table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
</dd>
<dt><a name="a10">I've seen references to Pluto 1.0.x and 1.1x. What are versions 1.x used for?</a></dt>
-<dd>
- <p>
- Pluto 1.0.x is based off of the code base which was
- originally donated to the ASF by IBM. The first release
- candidate in this series was published on October 8, 2004.
- Pluto 1.0.x is only maintained for bug fixes.
- </p>
- <p>
- Pluto 1.0.1 is the portlet container embedded in all Jetspeed release up until version 2.2.0.
- From version 2.2.0 onward, Jetspeed embeds Pluto 2.0.x.
- </p>
- <p>
- The 1.1.x series is a refactoring/rewrite of Pluto 1.0.x. It's
- entire purpose is to simplify the container and make it
- easier for both Portlet Developers and Portal Developers
- looking to embed Pluto into their portal to use Pluto.
- </p>
- <p>
- Now that Pluto 2.0.0 has been released, our team highly
- recommends that you migrate to it. Pluto 1.0.x development
- has been stagnant for some time and there are no plans to
- support it in the future.
- </p>
+<dd>
+ <p>
+ Pluto 1.0.x is based off of the code base which was
+ originally donated to the ASF by IBM. The first release
+ candidate in this series was published on October 8, 2004.
+ Pluto 1.0.x is only maintained for bug fixes.
+ </p>
+ <p>
+ Pluto 1.0.1 is the portlet container embedded in all Jetspeed release up until version 2.2.0.
+ From version 2.2.0 onward, Jetspeed embeds Pluto 2.0.x.
+ </p>
+ <p>
+ The 1.1.x series is a refactoring/rewrite of Pluto 1.0.x. It's
+ entire purpose is to simplify the container and make it
+ easier for both Portlet Developers and Portal Developers
+ looking to embed Pluto into their portal to use Pluto.
+ </p>
+ <p>
+ Now that Pluto 2.0.0 has been released, our team highly
+ recommends that you migrate to it. Pluto 1.0.x development
+ has been stagnant for some time and there are no plans to
+ support it in the future.
+ </p>
<table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
</dd>
<dt><a name="portal">Is Pluto an Enterprise Portal?</a></dt>
-<dd>
- No, the Pluto project aims to provide a Java Specification
- compliant Portlet Container. In order to support the container,
- the Pluto project provides a simple portal, however, this does
- not provides optional services such as single sign on. If you
- are looking for an Open Source enterprise Portal implementation,
- there are several available. Apache Jetspeed is an enterprise
- portal hosted by the Apache Software Foundation. Sakai and uPortal
- are both educational portals which utilize Pluto as their container.
- There are many other open source portals.
+<dd>
+ No, the Pluto project aims to provide a Java Specification
+ compliant Portlet Container. In order to support the container,
+ the Pluto project provides a simple portal, however, this does
+ not provides optional services such as single sign on. If you
+ are looking for an Open Source enterprise Portal implementation,
+ there are several available. Apache Jetspeed is an enterprise
+ portal hosted by the Apache Software Foundation. Sakai and uPortal
+ are both educational portals which utilize Pluto as their container.
+ There are many other open source portals.
<table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
</dd>
<dt><a name="simple-embed">What's the easiest way to include a portlet in my webapp (applies to Pluto 1.x only)</a></dt>
-<dd>
- <p>
- Simple, use the Pluto Portal Drivers "PortalDriverFilter". This allows
- you to embed a portlet directly into a jsp page. To use it, do the following:
- </p>
- <p>
- <ul>
- <li>Add the Portal Driver listener Configuration to your web.xml
- <textarea style="border:0; width: 100%; background:transparent; color:#555555" rows="3" readonly="true">
-<listener>
- <listener-class>org.apache.pluto.driver.PortalStartupListener</listener-class>
-</listener>
- </textarea>
- </li>
- <li>Add the PortalDriverFilter configuration to your web.xml
- <textarea style="border:0; width: 100%; background:transparent; color:#555555" rows="15" readonly="true">
-<filter>
- <filter-name>plutoPortalDriver</filter-name>
- <filter-class>org.apache.pluto.driver.PortalDriverFilter</filter-class>
-</filter>
-
-<filter-mapping>
- <filter-name>plutoPortalDriver</filter-name>
- <url-pattern>/about.jsp</url-pattern>
-</filter-mapping>
-
-<filter-mapping>
- <filter-name>plutoPortalDriver</filter-name>
- <url-pattern>/about.jsp/*</url-pattern>
-</filter-mapping>
- </textarea>
- </li>
- <li>Include the portlet (and perhaps some controls?) in your jsp.
- <textarea style="border:0; width: 100%; background:transparent; color:#555555" rows="15" readonly="true">
-%@ taglib uri="http://portals.apache.org/pluto" prefix="pluto" %
-
-<pluto:portlet portletId="${portlet}">
- <div class="portlet" id=">c:out value="${portlet}"/>">
- <div class="header">
- <h2 class="title"><pluto:title></pluto:title></h2>
- </div>
- <div class="body">
- <pluto:render></pluto:render>
- </div>
- </div>
-</pluto:portlet>
- </textarea>
- </li>
- </ul>
- </p>
+<dd>
+ <p>
+ Simple, use the Pluto Portal Drivers "PortalDriverFilter". This allows
+ you to embed a portlet directly into a jsp page. To use it, do the following:
+ </p>
+ <p>
+ <ul>
+ <li>Add the Portal Driver listener Configuration to your web.xml
+ <textarea style="border:0; width: 100%; background:transparent; color:#555555" rows="3" readonly="true">
+<listener>
+ <listener-class>org.apache.pluto.driver.PortalStartupListener</listener-class>
+</listener>
+ </textarea>
+ </li>
+ <li>Add the PortalDriverFilter configuration to your web.xml
+ <textarea style="border:0; width: 100%; background:transparent; color:#555555" rows="15" readonly="true">
+<filter>
+ <filter-name>plutoPortalDriver</filter-name>
+ <filter-class>org.apache.pluto.driver.PortalDriverFilter</filter-class>
+</filter>
+
+<filter-mapping>
+ <filter-name>plutoPortalDriver</filter-name>
+ <url-pattern>/about.jsp</url-pattern>
+</filter-mapping>
+
+<filter-mapping>
+ <filter-name>plutoPortalDriver</filter-name>
+ <url-pattern>/about.jsp/*</url-pattern>
+</filter-mapping>
+ </textarea>
+ </li>
+ <li>Include the portlet (and perhaps some controls?) in your jsp.
+ <textarea style="border:0; width: 100%; background:transparent; color:#555555" rows="15" readonly="true">
+%@ taglib uri="http://portals.apache.org/pluto" prefix="pluto" %
+
+<pluto:portlet portletId="${portlet}">
+ <div class="portlet" id=">c:out value="${portlet}"/>">
+ <div class="header">
+ <h2 class="title"><pluto:title></pluto:title></h2>
+ </div>
+ <div class="body">
+ <pluto:render></pluto:render>
+ </div>
+ </div>
+</pluto:portlet>
+ </textarea>
+ </li>
+ </ul>
+ </p>
<table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
</dd>
<dt><a name="encoding">How can I change the default encoding of the Pluto Portal</a></dt>
-<dd>
- <p>
- This is currently not supported with Pluto 3.0. The character encoding for
- render requests is set to UTF-8.
- </p>
- <p>As of Pluto 1.1.5 you can change the default encoding of the Pluto Portal by
- editing the Pluto Portlet Servlet's web.xml. Add an init-param with
- the name of "charset" and set the value to the desired character set.</p>
- <textarea style="border:0; width: 100%; background:transparent; color:#555555" rows="15" readonly="true">
- <servlet>
- <servlet-name>plutoPortalDriver</servlet-name>
- <display-name>Pluto Portal Driver</display-name>
- <description>Pluto Portal Driver Controller</description>
- <servlet-class>org.apache.pluto.driver.PortalDriverServlet</servlet-class>
- <init-param>
- <param-name>charset</param-name>
- <param-value>UTF-8</param-value>
- </init-param>
- </servlet>
- </textarea>
+<dd>
+ <p>
+ This is currently not supported with Pluto 3.0. The character encoding for
+ render requests is set to UTF-8.
+ </p>
+ <p>As of Pluto 1.1.5 you can change the default encoding of the Pluto Portal by
+ editing the Pluto Portlet Servlet's web.xml. Add an init-param with
+ the name of "charset" and set the value to the desired character set.</p>
+ <textarea style="border:0; width: 100%; background:transparent; color:#555555" rows="15" readonly="true">
+ <servlet>
+ <servlet-name>plutoPortalDriver</servlet-name>
+ <display-name>Pluto Portal Driver</display-name>
+ <description>Pluto Portal Driver Controller</description>
+ <servlet-class>org.apache.pluto.driver.PortalDriverServlet</servlet-class>
+ <init-param>
+ <param-name>charset</param-name>
+ <param-value>UTF-8</param-value>
+ </init-param>
+ </servlet>
+ </textarea>
<table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
</dd>
-<dt><a name="xml-parsing">
- Do I need to have xml parsers in an endorsed classloader? (e.g.in
- Tomcat's 5.5 common/endorsed directory)
+<dt><a name="xml-parsing">
+ Do I need to have xml parsers in an endorsed classloader? (e.g.in
+ Tomcat's 5.5 common/endorsed directory)
</a></dt>
-<dd>
- <p>If you have installed Pluto 1.1.5 or greater, and are running on
- Java 5 or greater, then you do not need to endorse any XML
- libraries. Pluto will use JAXP.</p>
- <p>The Pluto 1.1.x codebase targets Java 1.4, and so the bundled
- distribution of Pluto includes Tomcat with XML libraries in
- <code>common/endorsed</code>. Simply remove the XML libraries
- from <code>common/endorsed</code> if you meet the above requirements.</p>
+<dd>
+ <p>If you have installed Pluto 1.1.5 or greater, and are running on
+ Java 5 or greater, then you do not need to endorse any XML
+ libraries. Pluto will use JAXP.</p>
+ <p>The Pluto 1.1.x codebase targets Java 1.4, and so the bundled
+ distribution of Pluto includes Tomcat with XML libraries in
+ <code>common/endorsed</code>. Simply remove the XML libraries
+ from <code>common/endorsed</code> if you meet the above requirements.</p>
<table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table></dd>
</dl>
@@ -426,7 +425,7 @@
</div>
<div id="footer">
<div class="xright">©
- 2004-2016
+ 2004-2017
Apache Software Foundation
Modified: portals/site-live/pluto/helping.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/helping.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/helping.html (original)
+++ portals/site-live/pluto/helping.html Fri Jan 13 11:55:02 2017
@@ -1,269 +1,269 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-
-
-
-
-
-
-
-
-
-
-<html xmlns="http://www.w3.org/1999/xhtml">
- <head>
- <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
- <title>Pluto - Getting Involved</title>
- <style type="text/css" media="all">
- @import url("./css/maven-base.css");
- @import url("./css/maven-theme.css");
- @import url("./css/site.css");
- </style>
- <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- </head>
- <body class="composite">
- <div id="banner">
- <a href="http://portals.apache.org/pluto/" id="bannerLeft">
-
- <img src="http://portals.apache.org/pluto/images/apache-portals.gif" alt="" />
-
- </a>
- <span id="bannerRight">
-
- <img src="http://portals.apache.org/pluto/images/banner.png" alt="" />
-
- </span>
- <div class="clear">
- <hr/>
- </div>
- </div>
- <div id="breadcrumbs">
-
-
-
-
-
-
-
-
- <div class="xleft">
- Last Published: 2016-12-02
- |
- <a href="http://portals.apache.org/pluto" class="externalLink">Home</a>
- </div>
- <div class="xright"> <a href="portlet-3.0-apidocs/index.html">Portlet 3.0 API</a>
- |
- <a href="portlet-2.0-apidocs/index.html">Portlet 2.0 API</a>
- |
- <a href="portlet-1.0-apidocs/index.html">Portlet 1.0 API</a>
- |
- <a href="http://jcp.org/en/jsr/detail?id=362" class="externalLink">JSR 362 JCP Page</a>
- |
- <a href="http://jcp.org/en/jsr/detail?id=286" class="externalLink">JSR 286 JCP Page</a>
- |
- <a href="http://jcp.org/en/jsr/detail?id=168" class="externalLink">JSR 168 JCP Page</a>
-
-
-
-
-
-
-
-
- </div>
- <div class="clear">
- <hr/>
- </div>
- </div>
- <div id="leftColumn">
- <div id="navcolumn">
-
-
-
-
-
-
-
-
- <h5>The Pluto Project</h5>
- <ul>
-
- <li class="none">
- <a href="index.html">About Pluto</a>
- </li>
-
- <li class="none">
- <a href="mission.html">Mission</a>
- </li>
-
- <li class="none">
- <a href="download.html">Download</a>
- </li>
-
- <li class="none">
- <a href="news.html">News</a>
- </li>
-
- <li class="none">
- <a href="status.html">Status</a>
- </li>
-
- <li class="none">
- <a href="architecture.html">Architecture</a>
- </li>
-
- <li class="none">
- <a href="resources.html">Resources</a>
- </li>
-
- <li class="none">
- <a href="faq.html">FAQ</a>
- </li>
-
- <li class="none">
- <a href="http://wiki.apache.org/portals/Pluto" class="externalLink">Wiki</a>
- </li>
-
- <li class="none">
- <a href="https://issues.apache.org/jira/browse/PLUTO" class="externalLink">Issue Tracker (JIRA)</a>
- </li>
-
- <li class="none">
- <strong>Get Involved</strong>
- </li>
- </ul>
- <h5>Pluto 3.0</h5>
- <ul>
-
- <li class="none">
- <a href="v30/getting-started.html">Getting Started</a>
- </li>
-
- <li class="none">
- <a href="v30/deploying.html">Deploying Portlets</a>
- </li>
-
- <li class="none">
- <a href="v30/portlet-api.html">Portlet Concepts</a>
- </li>
-
- <li class="none">
- <a href="v30/v3Features.html">Version 3 Features</a>
- </li>
-
- <li class="none">
- <a href="v30/tck.html">Using the TCK</a>
- </li>
-
- <li class="none">
- <a href="v30/release-notes.html">Release Notes</a>
- </li>
- </ul>
- <h5>Pluto 2.0</h5>
- <ul>
-
- <li class="none">
- <a href="v20/getting-started.html">Getting Started</a>
- </li>
-
- <li class="none">
- <a href="v20/deploying.html">Deploying</a>
- </li>
-
- <li class="none">
- <a href="v20/embedding.html">Embedding</a>
- </li>
-
- <li class="none">
- <a href="v20/release-notes.html">Release Notes</a>
- </li>
-
- <li class="none">
- <a href="v20/app-servers.html">App Servers</a>
- </li>
-
- <li class="none">
- <a href="v20/powered.html">Powered By Pluto</a>
- </li>
- </ul>
- <h5>Pluto 1.1</h5>
- <ul>
-
- <li class="none">
- <a href="v11/getting-started.html">Getting Started</a>
- </li>
-
- <li class="none">
- <a href="v11/deploying.html">Deploying</a>
- </li>
-
- <li class="none">
- <a href="v11/release-notes.html">Release Notes</a>
- </li>
- </ul>
- <h5>Subprojects</h5>
- <ul>
-
- <li class="none">
- <a href="subprojects/subprojects.html">Overview</a>
- </li>
- </ul>
- <h5>Project Info</h5>
- <ul>
-
- <li class="none">
- <a href="project-summary.html">Project Summary</a>
- </li>
-
- <li class="none">
- <a href="team-list.html">Project Team</a>
- </li>
-
- <li class="none">
- <a href="license.html">Project License</a>
- </li>
-
- <li class="none">
- <a href="mail-lists.html">Mailing Lists</a>
- </li>
-
- <li class="none">
- <a href="source-repository.html">Source Repository</a>
- </li>
-
- <li class="none">
- <a href="issue-tracking.html">Issue Tracking</a>
- </li>
- </ul>
- <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
- <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
- </a>
-
-
-
-
-
-
-
-
- </div>
- </div>
- <div id="bodyColumn">
- <div id="contentBox">
- <div class="section"><h2><a name="top">Getting Involved</a></h2>
-<ol type="1"><li><a href="#involved">Getting Involved</a></li>
-<li><a href="#mail">Joining the Mailing Lists</a></li>
-<li><a href="#patches">How do I create a patch?</a></li>
-<li><a href="#issues">How can I report defects or suggest features?</a></li>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+
+
+
+
+
+
+
+
+
+<html xmlns="http://www.w3.org/1999/xhtml">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
+ <title>Pluto - Getting Involved</title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ </head>
+ <body class="composite">
+ <div id="banner">
+ <a href="http://portals.apache.org/pluto/" id="bannerLeft">
+
+ <img src="http://portals.apache.org/pluto/images/apache-portals.gif" alt="" />
+
+ </a>
+ <span id="bannerRight">
+
+ <img src="http://portals.apache.org/pluto/images/banner.png" alt="" />
+
+ </span>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="breadcrumbs">
+
+
+
+
+
+
+
+
+ <div class="xleft">
+ Last Published: 2017-01-13
+ |
+ <a href="http://portals.apache.org/pluto" class="externalLink">Home</a>
+ </div>
+ <div class="xright"> <a href="portlet-3.0-apidocs/index.html">Portlet 3.0 API</a>
+ |
+ <a href="portlet-2.0-apidocs/index.html">Portlet 2.0 API</a>
+ |
+ <a href="portlet-1.0-apidocs/index.html">Portlet 1.0 API</a>
+ |
+ <a href="http://jcp.org/en/jsr/detail?id=362" class="externalLink">JSR 362 JCP Page</a>
+ |
+ <a href="http://jcp.org/en/jsr/detail?id=286" class="externalLink">JSR 286 JCP Page</a>
+ |
+ <a href="http://jcp.org/en/jsr/detail?id=168" class="externalLink">JSR 168 JCP Page</a>
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ <div id="leftColumn">
+ <div id="navcolumn">
+
+
+
+
+
+
+
+
+ <h5>The Pluto Project</h5>
+ <ul>
+
+ <li class="none">
+ <a href="index.html">About Pluto</a>
+ </li>
+
+ <li class="none">
+ <a href="mission.html">Mission</a>
+ </li>
+
+ <li class="none">
+ <a href="download.html">Download</a>
+ </li>
+
+ <li class="none">
+ <a href="news.html">News</a>
+ </li>
+
+ <li class="none">
+ <a href="status.html">Status</a>
+ </li>
+
+ <li class="none">
+ <a href="architecture.html">Architecture</a>
+ </li>
+
+ <li class="none">
+ <a href="resources.html">Resources</a>
+ </li>
+
+ <li class="none">
+ <a href="faq.html">FAQ</a>
+ </li>
+
+ <li class="none">
+ <a href="http://wiki.apache.org/portals/Pluto" class="externalLink">Wiki</a>
+ </li>
+
+ <li class="none">
+ <a href="https://issues.apache.org/jira/browse/PLUTO" class="externalLink">Issue Tracker (JIRA)</a>
+ </li>
+
+ <li class="none">
+ <strong>Get Involved</strong>
+ </li>
+ </ul>
+ <h5>Pluto 3.0</h5>
+ <ul>
+
+ <li class="none">
+ <a href="v30/getting-started.html">Getting Started</a>
+ </li>
+
+ <li class="none">
+ <a href="v30/deploying.html">Deploying Portlets</a>
+ </li>
+
+ <li class="none">
+ <a href="v30/portlet-api.html">Portlet Concepts</a>
+ </li>
+
+ <li class="none">
+ <a href="v30/v3Features.html">Version 3 Features</a>
+ </li>
+
+ <li class="none">
+ <a href="v30/tck.html">Using the TCK</a>
+ </li>
+
+ <li class="none">
+ <a href="v30/release-notes.html">Release Notes</a>
+ </li>
+ </ul>
+ <h5>Pluto 2.0</h5>
+ <ul>
+
+ <li class="none">
+ <a href="v20/getting-started.html">Getting Started</a>
+ </li>
+
+ <li class="none">
+ <a href="v20/deploying.html">Deploying</a>
+ </li>
+
+ <li class="none">
+ <a href="v20/embedding.html">Embedding</a>
+ </li>
+
+ <li class="none">
+ <a href="v20/release-notes.html">Release Notes</a>
+ </li>
+
+ <li class="none">
+ <a href="v20/app-servers.html">App Servers</a>
+ </li>
+
+ <li class="none">
+ <a href="v20/powered.html">Powered By Pluto</a>
+ </li>
+ </ul>
+ <h5>Pluto 1.1</h5>
+ <ul>
+
+ <li class="none">
+ <a href="v11/getting-started.html">Getting Started</a>
+ </li>
+
+ <li class="none">
+ <a href="v11/deploying.html">Deploying</a>
+ </li>
+
+ <li class="none">
+ <a href="v11/release-notes.html">Release Notes</a>
+ </li>
+ </ul>
+ <h5>Subprojects</h5>
+ <ul>
+
+ <li class="none">
+ <a href="subprojects/subprojects.html">Overview</a>
+ </li>
+ </ul>
+ <h5>Project Info</h5>
+ <ul>
+
+ <li class="none">
+ <a href="project-summary.html">Project Summary</a>
+ </li>
+
+ <li class="none">
+ <a href="team-list.html">Project Team</a>
+ </li>
+
+ <li class="none">
+ <a href="license.html">Project License</a>
+ </li>
+
+ <li class="none">
+ <a href="mail-lists.html">Mailing Lists</a>
+ </li>
+
+ <li class="none">
+ <a href="source-repository.html">Source Repository</a>
+ </li>
+
+ <li class="none">
+ <a href="issue-tracking.html">Issue Tracking</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
+ </a>
+
+
+
+
+
+
+
+
+ </div>
+ </div>
+ <div id="bodyColumn">
+ <div id="contentBox">
+ <div class="section"><h2><a name="top">Getting Involved</a></h2>
+<ol type="1"><li><a href="#involved">Getting Involved</a></li>
+<li><a href="#mail">Joining the Mailing Lists</a></li>
+<li><a href="#patches">How do I create a patch?</a></li>
+<li><a href="#issues">How can I report defects or suggest features?</a></li>
<li><a href="#contribute">How can I contribute to the Pluto source
- code?</a></li>
+ code?</a></li>
<li><a href="#documentation">How can I contribute to the
- documentation?</a></li>
-<li><a href="#release">So when is the next release coming out?</a></li>
-<li><a href="#decides_help">How can I help make the decisions?</a></li>
-</ol>
-</div>
-<dl><dt><a name="involved">Getting Involved</a></dt>
+ documentation?</a></li>
+<li><a href="#release">So when is the next release coming out?</a></li>
+<li><a href="#decides_help">How can I help make the decisions?</a></li>
+</ol>
+</div>
+<dl><dt><a name="involved">Getting Involved</a></dt>
<dd>
<p>
@@ -334,9 +334,9 @@
Your feedback helps the technology to evolve.
</p>
- <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
-</dd>
-<dt><a name="mail">Joining the Mailing Lists</a></dt>
+ <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
+</dd>
+<dt><a name="mail">Joining the Mailing Lists</a></dt>
<dd>
<p>
@@ -353,9 +353,9 @@
HTML</a>
in your email client before posting.
</p>
- <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
-</dd>
-<dt><a name="patches">How do I create a patch?</a></dt>
+ <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
+</dd>
+<dt><a name="patches">How do I create a patch?</a></dt>
<dd>
<p>
A patch is a machine-readable script that can
@@ -422,9 +422,9 @@
subject of creating patches.
</p>
- <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
-</dd>
-<dt><a name="issues">How can I report defects or suggest features?</a></dt>
+ <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
+</dd>
+<dt><a name="issues">How can I report defects or suggest features?</a></dt>
<dd>
<p>
Tracking of defect reports and enhancement suggestions for
@@ -480,10 +480,10 @@
tracker.</a>
</p>
- <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
-</dd>
+ <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
+</dd>
<dt><a name="contribute">How can I contribute to the Pluto source
- code?</a></dt>
+ code?</a></dt>
<dd>
<p>
@@ -522,19 +522,19 @@
file containing your patch.
</p>
- <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
-</dd>
+ <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
+</dd>
<dt><a name="documentation">How can I contribute to the
- documentation?</a></dt>
+ documentation?</a></dt>
<dd>
<p>
The same way you contribute to the source code. All
documentation is generated using maven.
</p>
- <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
-</dd>
-<dt><a name="release">So when is the next release coming out?</a></dt>
+ <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
+</dd>
+<dt><a name="release">So when is the next release coming out?</a></dt>
<dd>
<p>
@@ -617,9 +617,9 @@
This way you are at least forewarned and forearmed.
</p>
- <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
-</dd>
-<dt><a name="decides_help">How can I help make the decisions?</a></dt>
+ <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table><hr />
+</dd>
+<dt><a name="decides_help">How can I help make the decisions?</a></dt>
<dd>
<p>
@@ -684,31 +684,31 @@
and the
</p>
- <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table></dd>
-</dl>
-
- </div>
- </div>
- <div class="clear">
- <hr/>
- </div>
- <div id="footer">
- <div class="xright">©
- 2004-2016
-
- Apache Software Foundation
-
-
-
-
-
-
-
-
- </div>
- <div class="clear">
- <hr/>
- </div>
- </div>
- </body>
-</html>
+ <table border="0"><tr><td align="right"><a href="#top">[top]</a></td></tr></table></dd>
+</dl>
+
+ </div>
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ <div id="footer">
+ <div class="xright">©
+ 2004-2017
+
+ Apache Software Foundation
+
+
+
+
+
+
+
+
+ </div>
+ <div class="clear">
+ <hr/>
+ </div>
+ </div>
+ </body>
+</html>
Modified: portals/site-live/pluto/index.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/index.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/index.html (original)
+++ portals/site-live/pluto/index.html Fri Jan 13 11:55:02 2017
@@ -47,7 +47,7 @@
<div class="xleft">
- Last Published: 2016-12-02
+ Last Published: 2017-01-13
|
<a href="http://portals.apache.org/pluto" class="externalLink">Home</a>
</div>
@@ -251,85 +251,85 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section"><h2><a name="Welcome_to_Pluto"></a>Welcome to Pluto</h2>
-<div class="highlightBox"><h5>Get Pluto 2.0.3</h5>
-<p><a class="externalLink" href="http://www.apache.org/dyn/closer.cgi/portals/pluto/"><img src="images/download.gif" />
- Download
- </a>
- Pluto 2.0.3
+<div class="highlightBox"><h5>Get Pluto 3.0.0</h5>
+<p><a href="http://www.apache.org/dyn/closer.cgi/portals/pluto/" class="externalLink"><img src="images/download.gif" />
+ Download
+ </a>
+ Pluto 3.0.0
</p>
-<ul><li><a href="v20/getting-started.html">Installation Guide</a></li>
+<ul><li><a href="v30/getting-started.html">Installation Guide</a></li>
</ul>
-</div><p>
- The Apache Pluto project hosts the Java Portlet Specification Reference Implementation (RI) and Technology Compliance Kit (TCK).
- The current version (3.0) of this specification is known as <a class="externalLink" href="http://jcp.org/en/jsr/detail?id=362">JSR-362</a>.
- The previous specification version, <a class="externalLink" href="http://jcp.org/en/jsr/detail?id=286">JSR-286</a>, covers
- version 2.0 of the specification.
- The first version of the specification, <a class="externalLink" href="http://jcp.org/en/jsr/detail?id=168">JSR-168</a>, established
- version 1.0. Pluto implements and is fully compliant with all three of these specifications.
+</div><p>
+ The Apache Pluto project hosts the Java Portlet Specification Reference Implementation (RI) and Technology Compliance Kit (TCK).
+ The current version (3.0) of this specification is known as <a href="http://jcp.org/en/jsr/detail?id=362" class="externalLink">JSR-362</a>.
+ The previous specification version, <a href="http://jcp.org/en/jsr/detail?id=286" class="externalLink">JSR-286</a>, covers
+ version 2.0 of the specification.
+ The first version of the specification, <a href="http://jcp.org/en/jsr/detail?id=168" class="externalLink">JSR-168</a>, established
+ version 1.0. Pluto implements and is fully compliant with all three of these specifications.
</p>
</div>
<div class="section"><h2><a name="Pluto_implements_a_Portlet_Container"></a>Pluto implements a Portlet Container</h2>
-<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 Pluto portlet container
- does not work stand-alone like the servlet container; instead it is
- implemented as a thin layer on top of the servlet container and reuses
- servlet container functionality. From an architecture point of view,
- the Pluto portlet container provides an interface between the portal and portlets.
+<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 Pluto portlet container
+ does not work stand-alone like the servlet container; instead it is
+ implemented as a thin layer on top of the servlet container and reuses
+ servlet container functionality. From an architecture point of view,
+ the Pluto portlet container provides an interface between the portal and portlets.
</p>
-<p>
- Pluto serves as the portlet container for many portals, including <a class="externalLink" href="http://portals.apache.org/jetspeed-2/">Apache Jetspeed</a>. To
- accommodate the aggregation and display of diverse content in a dynamic
- manner, a portal such as Jetspeed must provide a framework that
- integrates the various pluggable parts into a consistent user interface
- for the portal user. The pluggable parts are called <i>portlets</i>. The
- contract, or programming API, between these portlets and a portal is
- known as the Portlet API. Pluto is the implementation of this contract
- or API.
+<p>
+ Pluto serves as the portlet container for many portals, including <a href="http://portals.apache.org/jetspeed-2/" class="externalLink">Apache Jetspeed</a>. To
+ accommodate the aggregation and display of diverse content in a dynamic
+ manner, a portal such as Jetspeed must provide a framework that
+ integrates the various pluggable parts into a consistent user interface
+ for the portal user. The pluggable parts are called <i>portlets</i>. The
+ contract, or programming API, between these portlets and a portal is
+ known as the Portlet API. Pluto is the implementation of this contract
+ or API.
</p>
-<p>
- Portlets are designed to be independent applications, just as servlets
- are. However, rather than producing a complete web page, portlets
- produce markup fragments that are intended to be aggregated with the
- output from other portlets to produce a complete portal page. Portlets
- can be developed without knowledge of the other portlets that the portal
- places on the resulting web page. They need only obey the syntactic and
- semantic rules laid out by the portlet specification.
+<p>
+ Portlets are designed to be independent applications, just as servlets
+ are. However, rather than producing a complete web page, portlets
+ produce markup fragments that are intended to be aggregated with the
+ output from other portlets to produce a complete portal page. Portlets
+ can be developed without knowledge of the other portlets that the portal
+ places on the resulting web page. They need only obey the syntactic and
+ semantic rules laid out by the portlet specification.
</p>
</div>
<div class="section"><h2><a name="Pluto_Provides_a_Light-Weight_In-Memory_Portal"></a>Pluto Provides a Light-Weight, In-Memory Portal</h2>
-<p>
- The Pluto portlet container fully implements the Portlet API
- specification and offers developers a working example platform on
- which they can test their portlets. However, it is cumbersome to execute
- and test the portlet container without a driver such as a full running
- portal. To aid in portlet development and testing, and to provide a
- framework for testing the portlet container itself, Pluto provides a
- simple portal component that fulfills the requirements set out by the
- JSR 362 Portlet Specification 3.0 standard.
+<p>
+ The Pluto portlet container fully implements the Portlet API
+ specification and offers developers a working example platform on
+ which they can test their portlets. However, it is cumbersome to execute
+ and test the portlet container without a driver such as a full running
+ portal. To aid in portlet development and testing, and to provide a
+ framework for testing the portlet container itself, Pluto provides a
+ simple portal component that fulfills the requirements set out by the
+ JSR 362 Portlet Specification 3.0 standard.
</p>
-<p>
- The term "in-memory" means that the Pluto portal component does not provide
- a mechanism for data persistence. For example, portlets may set portlet
- preferences, but Pluto does not persist the preference data across a server
- restart.
+<p>
+ The term "in-memory" means that the Pluto portal component does not provide
+ a mechanism for data persistence. For example, portlets may set portlet
+ preferences, but Pluto does not persist the preference data across a server
+ restart.
</p>
-<p>If you want to get started with rapid portlet development with Pluto,
- see the documentation on
+<p>If you want to get started with rapid portlet development with Pluto,
+ see the documentation on
<a href="v30/getting-started.html">Developing with Pluto</a></p>
</div>
<div class="section"><h2><a name="How_Portlets_Differ_from_Servlets"></a>How Portlets Differ from Servlets</h2>
-<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. Also, portlets are generally administrated more dynamically than
- servlets.
+<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. Also, portlets are generally administrated more dynamically than
+ servlets.
</p>
</div>
@@ -340,7 +340,7 @@
</div>
<div id="footer">
<div class="xright">©
- 2004-2016
+ 2004-2017
Apache Software Foundation
Modified: portals/site-live/pluto/issue-tracking.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/issue-tracking.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/issue-tracking.html (original)
+++ portals/site-live/pluto/issue-tracking.html Fri Jan 13 11:55:02 2017
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.6 at 2016-12-02 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.6 at 2017-01-13 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -10,7 +10,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20161202" />
+ <meta name="Date-Revision-yyyymmdd" content="20170113" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -30,7 +30,7 @@
<div class="xleft">
- <span id="publishDate">Last Published: 2016-12-02</span>
+ <span id="publishDate">Last Published: 2017-01-13</span>
| <a href="./" title="Home">Home</a>
>
Issue Tracking
@@ -198,7 +198,7 @@
</div>
<div id="footer">
<div class="xright">
- Copyright © 2003–2016
+ Copyright © 2003–2017
<a href="http://www.apache.org/">The Apache Software Foundation</a>.
All rights reserved.
Modified: portals/site-live/pluto/license.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/license.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/license.html (original)
+++ portals/site-live/pluto/license.html Fri Jan 13 11:55:02 2017
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.6 at 2016-12-02 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.6 at 2017-01-13 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -10,7 +10,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20161202" />
+ <meta name="Date-Revision-yyyymmdd" content="20170113" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -30,7 +30,7 @@
<div class="xleft">
- <span id="publishDate">Last Published: 2016-12-02</span>
+ <span id="publishDate">Last Published: 2017-01-13</span>
| <a href="./" title="Home">Home</a>
>
Project License
@@ -401,7 +401,7 @@
</div>
<div id="footer">
<div class="xright">
- Copyright © 2003–2016
+ Copyright © 2003–2017
<a href="http://www.apache.org/">The Apache Software Foundation</a>.
All rights reserved.
Modified: portals/site-live/pluto/mail-lists.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/mail-lists.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/mail-lists.html (original)
+++ portals/site-live/pluto/mail-lists.html Fri Jan 13 11:55:02 2017
@@ -1,5 +1,5 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-<!-- Generated by Apache Maven Doxia Site Renderer 1.6 at 2016-12-02 -->
+<!-- Generated by Apache Maven Doxia Site Renderer 1.6 at 2017-01-13 -->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -10,7 +10,7 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta name="Date-Revision-yyyymmdd" content="20161202" />
+ <meta name="Date-Revision-yyyymmdd" content="20170113" />
<meta http-equiv="Content-Language" content="en" />
</head>
@@ -30,7 +30,7 @@
<div class="xleft">
- <span id="publishDate">Last Published: 2016-12-02</span>
+ <span id="publishDate">Last Published: 2017-01-13</span>
| <a href="./" title="Home">Home</a>
>
Project Mailing Lists
@@ -218,7 +218,7 @@
</div>
<div id="footer">
<div class="xright">
- Copyright © 2003–2016
+ Copyright © 2003–2017
<a href="http://www.apache.org/">The Apache Software Foundation</a>.
All rights reserved.
Modified: portals/site-live/pluto/mission.html
URL: http://svn.apache.org/viewvc/portals/site-live/pluto/mission.html?rev=1778563&r1=1778562&r2=1778563&view=diff
==============================================================================
--- portals/site-live/pluto/mission.html (original)
+++ portals/site-live/pluto/mission.html Fri Jan 13 11:55:02 2017
@@ -47,7 +47,7 @@
<div class="xleft">
- Last Published: 2016-12-02
+ Last Published: 2017-01-13
|
<a href="http://portals.apache.org/pluto" class="externalLink">Home</a>
</div>
@@ -251,54 +251,54 @@
<div id="bodyColumn">
<div id="contentBox">
<div class="section"><h2><a name="The_Pluto_Project_Mission"></a>The Pluto Project Mission</h2>
-<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.
- This following document attempts to clarify the development priorities
- of the Apache Pluto project.
+<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.
+ This 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>
+ 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>
+ 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>
+ 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>
+ 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>
+ 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>
</div>
@@ -309,7 +309,7 @@
</div>
<div id="footer">
<div class="xright">©
- 2004-2016
+ 2004-2017
Apache Software Foundation