Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/maven/the-need-for-a-custom-lifecycle.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/maven/the-need-for-a-custom-lifecycle.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/maven/the-need-for-a-custom-lifecycle.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/maven/the-need-for-a-custom-lifecycle.xml Tue Dec 2 00:53:22 2008
@@ -0,0 +1,265 @@
+<?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.
+
+ $Id$
+-->
+<document>
+ <properties>
+ <title>The need for a custom Maven build lifecycle</title>
+ <authors>
+ <person name="Ate Douma" email="ate@douma.nu" />
+ </authors>
+ </properties>
+ <body>
+ <section name="The need for a custom Maven build lifecycle">
+ <p>
+ A standard Maven 2.0 project provides 3 <em>fixed</em> build "lifecycles" called clean, default and site.<br/>
+ See also:
+ <a href="http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html">Introduction to the Build Lifecycle"</a>.
+ </p>
+ <p>
+ These standard build lifecycles all focus on, <em>and only on</em>, the project artifact(s) themselves.
+ This means the build lifecycle and all the possible configurations thereof really concerns the final artifact(s) itself,
+ <em>NOT</em> the (target) environment where it is intended to be used.
+ </p>
+ <p>
+ The final phase of the default lifecycle, <code>deploy</code>, concerns the deployment of the project artifact(s) to a remote Maven repository.
+ The intended <em>usage</em> of a deployed artifact comes only after this phase, and is in general out-of-scope from the POV of Maven itself,
+ except when such and artifact itself is used as dependency by another Maven project. (actually the most common, "expected" use-case).
+ </p>
+ <p>
+ For the most common Maven artifact type, jars, this is perfectly fine, but for application server integration frameworks like the Jetspeed-2 Portal,
+ it is <em>NOT</em>.
+ </p>
+ <p>
+ In contrast to more generic low-level (development) frameworks like Springframework, Jetspeed-2 comes with a very specific set of components usually
+ assembled and configured only on integration level. While Jetspeed-2 <em>itself</em> is assembled and configured using Maven-2 and Springframework on
+ a very low-level detail, it should require only a few specific configurations (and provide room for extensions) to adapt and integrate for a custom
+ project and its environment.
+ </p>
+ <p>
+ Furthermore, these custom project and enviroment specific changes and extensions should be possible separated from and independently of the base
+ Jetspeed-2 Portal components (and their base configuration) to allow proper maintainenance of the custom project lifecycle itself.
+ </p>
+ <p>For these requirements, the standard provided Maven build lifecycles and extension points are (currently) falling a bit short.</p>
+ <subsection name="Options to customizing the Maven build lifecycle">
+ <p>There are many ways to customize the Maven build lifecycle:</p>
+ <ol>
+ <li>
+ <b>Using (only) profiles</b>
+ <br />
+ <p>
+ Profiles within a Maven project (pom) file allows to augment or replace default lifecycle behavior, but <em>maintains</em>
+ the lifecycle phase handling. And because the default lifecycle already configures standard behavior, trying to achieve something very different
+ from the standard behavior (like deploying and configuring a complete Portal application for a specific application server) quickly becomes very
+ unwielding and difficult to setup and maintain (if at all).
+ </p>
+ <p>
+ </p>
+ </li>
+ <li>
+ <b>Using "standalone" plugins</b>
+ <br />
+ <p>
+ An alternative is writing and/or leveraging so called "standalone" Maven plugins which run <em>outside</em>
+ a lifecycle. These plugins don't affect or are affected by the default lifecycle. But... with the current Maven 2.0 model they can also only have
+ a single configuration within a project (pom) file, so many different tasks (and possible different environments) are needed, their configuration
+ quickly becomes very large and complex and/or require splitting them up using multiple profile definitions. But then, the complexity moves to
+ making sure the right profile combinations are executed which mean complex and error prone (manual) build instructions.
+ </p>
+ <p>
+ Furthermore, as these plugins run outside any lifecycle, none of the standard Maven plugins can be leveraged (nor directly "invoked" which isn't
+ supported by Maven). Often needed standard functionality like the default copying/filtering of resource files will have to be provided by the
+ standalone plugin itself too!
+ </p>
+ <p>
+ Finally, while a standalone plugin can "fork" off a default lifecycle (phase), this also means (potentially) <em>all</em>
+ the standard provided lifecycle behavior is executed too again, leading to the same problems as with the previous option (see: above).
+ </p>
+ </li>
+ <li>
+ <b>Using separate dedicated sub projects</b>
+ <br />
+ <p>
+ This is the "standard" Maven-2 solution if multiple "artifacts" are needed for a certain project: split the project up in separate sub projects
+ each providing its own "dedicated" result (note: with Maven-1 it was easy and common practice to write custom jelly "goals" in maven.xml for this
+ purpose).
+ </p>
+ <p>While this is certainly a good solution, and allows one to leverage the full Maven-2 feature set, it has a few caveats too.</p>
+ <p>
+ First of all, it can clutter the project structure quite a bit when many different "tasks" are required. Additionally, as these "tasks" usually
+ are not meant to be run automatically during the normal build lifecycle, they should not be configured as sub modules of a parent project but will
+ require manual navigation to and execution of by the developer. One could use (again) multiple profiles (see above) to "merge" several of these
+ tasks in one common project (pom) file, but this still requires the developer to know and specify each needed (combination of) profile(s) to
+ execute.
+ </p>
+ <p>
+ Additionally, while maybe "good" practice by itself, it also requires that all artifacts and resources needed by such a dedicated "task" project
+ are build and usually installed in the local or a remote Maven repository. This potentially adds additional complexity to a project configuration
+ when some resources already are available locally within the context of another (sub) project.
+ </p>
+ </li>
+ <li>
+ <b>Using custom project (pom) files</b>
+ <br />
+ <p>Maven-2 allows execution of non-default (pom.xml) project files using a command line option (-f <project file>).</p>
+ <p>
+ This solution elevates some of the caveats of the previous solution: there is no need to expand the project with several sub projects and a custom
+ "task" project file can directly access the project local resources.
+ </p>
+ <p>On the other hand, this solution now requires using additional command line parameters and thus again more effort from the developer.</p>
+ </li>
+ <li>
+ <b>Using a custom lifecycle extension</b>
+ <br />
+ <p>
+ Finally, it is possible to <em>replace</em> the default lifecycle of a project (pom) file alltogether by using a custom <packaging> type.
+ </p>
+ <p>
+ Such a custom lifecycle definition must be provided through a custom plugin extension and specifically configured within the project file. But the
+ custom lifecycle will have to provide the complete definition of all the intended behavior, and if that includes "old" standard behavior (like
+ building and installing a war) this solution quickly falls back again to the first option, albeit with more (but still fixed) flexibility and
+ choices for configuration.
+ </p>
+ <p>
+ Other caveats of this option are that probably multiple custom lifecycles are going to be required (e.g. different ones for pom,war,jar,ear etc.),
+ and that (future) default IDE tooling support will be very unlikely.
+ </p>
+ </li>
+ </ol>
+ <p>
+ Of the above options, option 2. and 5. are most difficult to maintain and use. Option 3. or 4., possibly combined with option 1. are more keeping in
+ line with the intended usage of Maven-2, but have as caveat that it requires more complex manual (commandline) usage instructions.
+ </p>
+ <p>
+ What really is missing here is some kind of automation: some kind of scripting/configuration of the different usages and required commandline
+ parameters as needed <em>for a specific custom project and its environment</em>
+ .
+ </p>
+ <p>
+ While writing custom shell scripts for just this purpose, or maybe even using a <a href="http://ant.apache.org">Apache Ant</a>
+ script to automate the different Maven-2 commands, this will easily will lead to every project having its own custom (and thus different) way of doing
+ things. And as it depends on yet another build tool incompatible environment problems (e.g. bash scripts usually don't run on Windows) are evident
+ too.
+ </p>
+ </subsection>
+ <subsection name="The jetspeed:mvn Maven Plugin - Automating Maven tasks using Maven">
+ <p>
+ To "solve" the problem described above, Jetspeed-2 provides a specific Maven plugin, jetspeed:mvn, which supports automating Maven-2 execution from
+ within Maven itself, using a configuration <em>within</em> a (parent) project file very similar to Apache Ant target definitions.
+ </p>
+ <p>
+ The jetspeed:mvn plugin <em>is</em> a standalone plugin (see discussion above), but requires only a very straightforward configuration and
+ only one additional runtime parameter to be specified on the commandline.
+ </p>
+ <p>
+ An example commandline usage and the configuration used within the Jetspeed-2 project build itself to build, install, configure the database and
+ finally deploy a full Jetspeed Demo Portal is: <source>$mvn jetspeed:mvn -Dtarget=demo</source>
+ <source><![CDATA[<plugin>
+ <groupId>org.apache.portals.jetspeed-2</groupId>
+ <artifactId>jetspeed-mvn-maven-plugin</artifactId>
+ <version>${org.apache.portals.jetspeed.version}</version>
+ <configuration>
+ <targets combine.children="append">
+ <target>
+ <id>testdb</id>
+ <name>db-init</name>
+ <properties>
+ <database.type>test</database.type>
+ </properties>
+ </target>
+ <target>
+ <id>proddb</id>
+ <name>db-init</name>
+ <properties>
+ <database.type>production</database.type>
+ </properties>
+ </target>
+ <target>
+ <id>demo-install</id>
+ <dir>@rootdir@/applications/jetspeed-demo</dir>
+ </target>
+ <target>
+ <id>demo-dbpsml-install</id>
+ <dir>@rootdir@/applications/jetspeed-demo</dir>
+ <profiles>dbpsml</profiles>
+ </target>
+ <target>
+ <id>demo-seed</id>
+ <name>demo</name>
+ <dir>@rootdir@/applications/jetspeed-demo</dir>
+ <profiles>seed</profiles>
+ </target>
+ <target>
+ <id>demo-seed-dbpsml</id>
+ <depends>demo-db</depends>
+ <name>demo</name>
+ <dir>@rootdir@/applications/jetspeed-demo</dir>
+ <profiles>seed-dbpsml</profiles>
+ </target>
+ <target>
+ <id>demo-deploy</id>
+ <name>demo</name>
+ <dir>@rootdir@/applications/jetspeed-demo</dir>
+ <profiles>deploy</profiles>
+ </target>
+ <target>
+ <id>demo-db</id>
+ <depends>proddb,demo-seed</depends>
+ </target>
+ <target>
+ <id>demo-db-psml</id>
+ <depends>demo-db,demo-seed-dbpsml</depends>
+ </target>
+ <target>
+ <id>demo</id>
+ <depends>demo-install,demo-db,demo-deploy</depends>
+ </target>
+ <target>
+ <id>demo-dbpsml</id>
+ <depends>demo-dbpsml-install,demo-db-psml,demo-deploy</depends>
+ </target>
+ </targets>
+ </configuration>
+</plugin>]]></source>
+ </p>
+ <p>
+ A target can optionally "depend" on other targets which then will be executed beforehand. Additionally, specific properties, profiles and goals can be
+ defined to be passed on to the Maven execution environment as well as (the location of) a custom project file to execute, and even a custom maven
+ settings file, allowing easy and <em>full</em> control of the target Maven execution environment.
+ </p>
+ <p>
+ The jetspeed:mvn plugin is based upon and adapted from the standard <a href="http://maven.apache.org/plugins/maven-invoker-plugin/">Maven Invoker Plugin</a>,
+ which is (only) targetted at running integration test projects as attached to the integration-test lifecycle phase.
+ </p>
+ <p>
+ The jetspeed:mvn expands upon the Invoker Plugin by allowing to be invoked directly from the commandline as well as providing a more generic and
+ configurable <em>chain</em> of execution targets, similar to Apache Ant build scripts, but fully using and delegating to standard Maven-2 project
+ build lifecycle handling for the actually execution of the individual target tasks.
+ </p>
+ <p>
+ Other than allowing execution from the commandline and the enhanced configuration options, the jetspeed:mvn doesn't really provide new behavior
+ compared to the standard Maven Invoker Plugin and uses the same Maven API and components (the shared maven-invoker component).
+ </p>
+ <p>
+ A full description and configuration definition for the jetspeed:mvn plugin is provided on the <a href="jetspeed-maven-plugins.html">Using jetspeed:mvn</a>
+ page. And example usages are also available from the "Examples" menu item to the left.
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>
\ No newline at end of file
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/maven/the-need-for-a-custom-lifecycle.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/maven/the-need-for-a-custom-lifecycle.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/new-security.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/new-security.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/new-security.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/new-security.xml Tue Dec 2 00:53:22 2008
@@ -0,0 +1,158 @@
+<?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>Security 2.2</title>
+ <subtitle>New Security in Version 2.2</subtitle>
+ <authors>
+ <person name="Dennis Dam" email="d.dam@onehippo.com" />
+ <person name="David Sean Taylor" email="taylor@apache.org" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Jetspeed Security Framework">
+ <subsection name="Key Concepts: Subjects, Principals, Credentials">
+ <p>
+Jetspeed supports Subject-based security as defined by JAAS (Java Authentication and Authorization Services).
+A subject is an aggregation of security information for a security entity, like a person.
+A subject can have several identities, also called principals. For example, a user logging into a
+Jetspeed portal is associated with one Subject, which contains a user principal, zero or more role principals, zero or more group principals, etc.
+Each principal can be associated with a set of permissions that allow the user to perform certain actions, like accessing a page, updating secured objects, etc.
+Finally, user principals in Jetspeed can be associated with a credential. A credential is, simply put, a username / password combination.
+ </p>
+ </subsection>
+ <subsection name="Jetspeed Security Component">
+ <p>
+All the security identity information above is managed by the Jetspeed Security Component. The Jetspeed Security Component provides a mechanism to access and update principal,
+ credential and permission data. When a user is authenticated in Jetspeed, a user principal is resolved for that user, based on the credentials that the user provided on login.
+ A user principal can then be associated with several other principals, which can be of the same (user principal) or different type (e.g. role, group, ..).
+ Principals are resolved in a nested manner, which means that each principal that is associated with the user principal can also be associated with other principals,
+ which can in turn be associated with other principals, etc. The final collection of principals found in this way is aggregated and attached to the Subject that is
+ resolved for the authenticated user. The Subject is used throughout Jetspeed for security purposed and can also be used by portlet applications to secure custom objects
+ using standard JAAS API.
+ </p>
+ </subsection>
+ <subsection name="Pluggable Security Architecture: Adapting to Different Security Models">
+ <p>
+Every project usually requires different security models, with meaningful relations between security principals that make sense for that project.
+Most projects can get away with using standard principal types like users, roles and groups, with regular associations between those principal types,
+like a user being a member of a role or group, a group being a member of a role, etc. There are also projects however, which go beyond that and require
+new principal types and custom associations between principal types. These projects create the need for a pluggable security architecture where new principal types
+ and principal associations can be added easily. This is exactly what the Jetspeed Security Component provides. This is best explained by illustrating
+ a custom security model, where a user is related to an organization. Jetspeed contains built-in support for users, groups and roles and associations between those,
+ but not for organizations and associations between users and organizations. To achieve that though, the following changes can be made to plugin organizations:
+ </p>
+<ul>
+<li>create a new class "Organization", implementing JetspeedPrincipal</li>
+<li>implement an OrganizationManager, based on the BaseJetspeedPrincipalManager.</li>
+<li>configure an "isMemberOf" association handler between a user and organization principal type</li>
+</ul>
+ <p>
+The OrganizationManager is a strongly typed manager with methods for accessing and storing organizations. The BaseJetspeedPrincipalManager class however, is a weakly typed manager,
+ which only operates on abstract principals. This means that for the most part, the OrganizationManager class can delegate back to the base class, except for some specific
+ organization handling and typecasting abstract principals back to organization instances.
+ </p>
+ <p>
+Configuring an association between users and organizations is in this case very simple, because an "isMemberOf" association handler is provided by default by Jetspeed.
+Configuring it is a matter of specifying a new instance of that handler and wiring it to both the UserManager and the OrganizationManager.
+ The custom security model setup is depicted in Figure 1.
+ <img src="images/extending-organization.jpg"/>
+ <i>Figure 1: Extending the security model with organizations</i>
+ </p>
+ </subsection>
+ <subsection name="Principals and Attributes">
+ <p>
+A Jetspeed principal is basically nothing more than a set of security attributes describing the principal.
+The attributes are custom and can differ per project. A user principal for example, can have contact information attributes.
+ An organization principal (from the example above) can have geographical coordinates of the office as an attribute.
+ The set of allowed attributes can be configured through Spring for each principal type.
+ Besides the attributes, a principal also has several constraints in its usage and access that can be configured,
+ such as whether the principal is read-only, can be removed, is enabled, etc.
+ </p>
+ </subsection>
+ <subsection name="Principal Associations">
+ <p>
+A principal association is a relation between two principals, where the relation always has a direction: it goes from one principal to another. For example,
+ in the relation "user is part of a group", the user is the starting point of the relation (the from principal) and the group is the ending point of the relation (the to principal).
+ The naming convention using "to" and "from" is used in the Jetspeed Security API. An example is a method in the JetspeedPrincipalManager interface called getAssociatedTo(..),
+ which fetches a list of associated principals given the name of a principal representing the "to" side of the association, and given the type of association.
+ The list of principals returned represent the "from" principals in the association. Associations have several characteristics, that influence the creation and deletion of
+ the principals in the association, or affect the way associations can be made between principals. The following list contains an overview of these characteristics:
+ </p>
+ <table>
+ <tr>
+ <th>Characteristic</th>
+ <th> Description</th>
+ </tr>
+ <tr>
+ <td>required</td>
+ <td>the "from" principal cannot be created without this association</td>
+ </tr>
+ <tr>
+ <td>dependent</td>
+ <td>the "from" principal will be deleted when the "to" principal is deleted</td>
+ </tr>
+ <tr>
+ <td>singular</td>
+ <td>the "from" principal can be associated from at most once</td>
+ </tr>
+ <tr>
+ <td>dominant</td>
+ <td>the "to" principal can be associated to at most once</td>
+ </tr>
+ </table>
+ <p>
+ All these characteristics are configured for an association through Spring.
+ </p>
+ <p>
+The built-in implementations of associations by Jetspeed are (and should be) independent of specific principal types. The advantage of that is that associations
+are pluggable and can be re-used between different pairs of principal types.
+ </p>
+ </subsection>
+ <subsection name="Storage of Principals and Associations">
+ <p>
+The storage engine of the Jetspeed Security Component uses a database to store and retrieve security data. By only allowing one type of data store,
+the storage and retrieval methods used internally by Jetspeed can be optimized and fine-tuned. An additional advantage is that more complex queries
+ on security data are possible, which would be difficult to achieve if the storage engine was abstracted in such a way that any data store could be supported.
+ </p>
+ <p>
+If the security model in Jetspeed is extended with new principals and/or associations, nothing has to be changed in database scripts or other code related to database.
+Jetspeed's generic storage engine will take care of storing and retrieving data.
+Although the storage engine works on top of a database internally, you have the possibility to synchronize data from another datastore. This will be discussed in the next section.
+ </p>
+ </subsection>
+ <subsection name="Synchronization and Replication">
+ <p>
+Security data can be synchronized from an external data store, and mapped to the database used internally by Jetspeed. Currently, LDAP is the only type of external
+data store supported by Jetspeed. LDAP data can be synchronized periodically, on startup or on authentication of a user. When synchronizing on authentication of a user,
+only the data related to that user is synchronized. Replication refers to writing back security data to the external store whenever security data in the database is updated.
+Synchronization is a mechanism which ensures that the contents of the external data store are the same as the internal database, where the external datastore has the highest
+priority. LDAP synchronization and replication is discussed in more detail in the LDAP Mapping guide.
+ </p>
+ </subsection>
+ <subsection name="Credentials">
+ <p>
+ </p>
+ </subsection>
+ <subsection name="Permissions">
+ <p>
+ </p>
+ </subsection>
+ </section>
+ </body>
+</document>
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/new-security.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/new-security.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/portlets-community.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/portlets-community.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/portlets-community.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/portlets-community.xml Tue Dec 2 00:53:22 2008
@@ -0,0 +1,56 @@
+<?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>Portlets Community</title>
+ <subtitle>Portlets Community</subtitle>
+ <authors>
+ <person name="David Le Strat" email="dlestrat@apache.org" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Portlets Community">
+ <table>
+ <tr>
+ <th>Project</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><a href="https://gems.dev.java.net/"><img src="images/portlets/gems.gif" border="0" /></a></td>
+ <td><a href="https://gems.dev.java.net/">Gems</a> provides a collection of JSR-168 portlets. The list of available portlets include:
+ <ul>
+ <li>E-Mail Portlet</li>
+ <li>Calendar Portlet</li>
+ <li>Blog Portlet</li>
+ <li>RSS Feed Portlet</li>
+ <li>Calculator Portlet</li>
+ <li>Image Viewer Portlet</li>
+ <li>Horoscope Portlet</li>
+ </ul></td>
+ </tr>
+ <tr>
+ <td><a href="http://sourceforge.jp/projects/pal/"><img src="http://pal.sourceforge.jp/images/pal-logo.png" border="0" /></a></td>
+ <td>
+ <a href="http://sourceforge.jp/projects/pal/">PAL</a> provides a useful JSR-168 portlets, such as File Manager, Blog, Yahoo! Japan Search portlets.
+ </td>
+ </tr>
+ </table>
+ </section>
+ </body>
+</document>
+
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/portlets-community.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/portlets-community.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/quality-testing.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/quality-testing.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/quality-testing.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/quality-testing.xml Tue Dec 2 00:53:22 2008
@@ -0,0 +1,58 @@
+<?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>Jetspeed Quality Testing</title>
+ <subtitle>Jetspeed Quality Testing Results</subtitle>
+ <authors>
+ <person name="David Sean Taylor" email="taylor@apache.org"/>
+ </authors>
+ </properties>
+ <body>
+<section name="Jetspeed Build and Quality Testing">
+<p>
+<a href='http://www.spikesource.com'>SpikeSource</a> runs nightly builds of Jetspeed-2 on a set of Linux
+platforms (Suse, Fedora, Redhat...). The builds run an entire Jetspeed-2 build and all unit tests. Additionally,
+code coverage tests are run. The results of these tests are available at the SpikeSource website.
+</p>
+<subsection name='Jetspeed-2 Build Results'>
+<p>Jetspeed-2 is built nightly. Unit tests and code coverage results are found here:</p>
+<p>
+<a href='http://www.spikesource.com/spikewatch/index.jsp?show=stat&show-test=true&component=jetspeed&platform=8'>Jetspeed-2 Nightly Build Results</a>
+</p>
+</subsection>
+<subsection name='Jetspeed-2 Build Results: REST'>
+<p>Jetspeed-2 is built nightly. Unit tests and code coverage results in REST format are found here:</p>
+<p>
+<a href='http://webgate.spikesource.com/spikewatch/ws/spikewatch.jsp?method=get-component-test-summary&partnerid=2&platform-id=&component-name=jetspeed&component-version='>Jetspeed-2 Nightly Build Results - REST</a>
+</p>
+</subsection>
+<subsection name='Open Source Build Results'>
+<p>Find the results of Jetspeed-2 and other open source builds here:</p>
+<p>
+<a href='http://www.spikesource.com/spikewatch/index.jsp'>Open Source Build Results</a>
+</p>
+</subsection>
+
+</section>
+
+</body>
+</document>
+
+
+
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/quality-testing.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/quality-testing.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.2.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.2.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.2.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.2.xml Tue Dec 2 00:53:22 2008
@@ -0,0 +1,123 @@
+<?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>Jetspeed-2 Release Notes</title>
+ <subtitle>Jetspeed-2 Release Notes</subtitle>
+ <authors>
+ <person name="Ate Douma" email="ate@douma.nu" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Release Notes - Jetspeed 2 - Version 2.1.2">
+ <p>
+ The list below outlines the issues that are addressed with release 2.1.2 For a full list of features, see the
+ <a href="features.html">features list</a>.
+ </p>
+ <p>
+ And the release notes of the previous major release 2.1 are available here: <a href="release-notes-2.1.html">release notes 2.1</a>.
+ </p>
+ <subsection name="Bug">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-282'>JS2-282</a>] - Error when session expires and portlet window is maximized</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-471'>JS2-471</a>] - Document Derby as the default database</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-484'>JS2-484</a>] - UserDetailsPortlet doesn't "see" newly added roles until after logging out and in again</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-502'>JS2-502</a>] - cannot disable user</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-512'>JS2-512</a>] - Profiler admin portlet can not display other language except English.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-525'>JS2-525</a>] - Roles and Groups appear in the User Details portlet when having been deleted</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-566'>JS2-566</a>] - Tapestry portlet's header doesn't display in jetspeed</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-580'>JS2-580</a>] - localization SSO Details portlet</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-657'>JS2-657</a>] - Installer fails with firewall</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-660'>JS2-660</a>] - Request attribute not available in jsp when using the JetspeedPowerTool</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-661'>JS2-661</a>] - Error in the antinstall-config script</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-665'>JS2-665</a>] - Duplicate Objects creation</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-667'>JS2-667</a>] - Portlet Selector is not returning to the correct page after navigation</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-668'>JS2-668</a>] - Adding Portlets to multiple layouts always adds to the top level layout</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-669'>JS2-669</a>] - Site Manager Admin portlet does not allow copying of a resource into the same folder where it exists</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-670'>JS2-670</a>] - Fragment Security Constraints only check View Mode</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-674'>JS2-674</a>] - Site component fails on profile navigations for subsites</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-675'>JS2-675</a>] - Site Manager Admin portlet: cannot view pages located via profiling rules with navigations or controls</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-681'>JS2-681</a>] - Login portlet doesn't run in Tomcat ROOT context</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-682'>JS2-682</a>] - Jetspeed thread waiting to lock for infinity time</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-687'>JS2-687</a>] - jetspeed deployment engine removes WEB-INF/tld/portlet.tld from portlet app web archive</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-688'>JS2-688</a>] - Unable to use Jetspeed services</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-689'>JS2-689</a>] - Spring Bean Factory creation of Prototype (non-singleton) beans causes serious performance degradation under load</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-690'>JS2-690</a>] - Caching issue with Print Mode</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-692'>JS2-692</a>] - Fragment ids are not automatically created, causing runtime errors</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-693'>JS2-693</a>] - Portal Site Manager error in java script for button "view" </li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-694'>JS2-694</a>] - actionResponse.sendRedirect("some psml page.psml") fails on the desktop</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-696'>JS2-696</a>] - Creating actionURLs on the desktop with javascript: tags in them fails</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-697'>JS2-697</a>] - Maximized mode overlaps as popup on desktop</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-698'>JS2-698</a>] - Minimized mode functions only in un-tiled state on desktop</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-699'>JS2-699</a>] - When going back from view mode to edit mode, icon is not always updated on desktop</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-703'>JS2-703</a>] - Remove Print Mode Window Decoration on Desktop</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-705'>JS2-705</a>] - Desktop window dragging mouse position offset bug</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-714'>JS2-714</a>] - Filter Admin users from delegated-security portlets</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-717'>JS2-717</a>] - MenuElement interface does not support getUrl method</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-718'>JS2-718</a>] - forgot pass portlet: password reset link does not work</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-719'>JS2-719</a>] - Default ehcache configuration is setup for distributed operation which will fail the portal to startup when no network is available</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-725'>JS2-725</a>] - Dociumentation mismatch </li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-727'>JS2-727</a>] - Appy Findbugs patches</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-731'>JS2-731</a>] - DESKTOP_ATTRIBUTE should be DESKTOP_CONTEXT_ATTRIBUTE</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-733'>JS2-733</a>] - Desktop: non-movable portlets are deletable</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-735'>JS2-735</a>] - Jetty-6 ConcurrentModificationException on logout</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-737'>JS2-737</a>] - Desktop doesn't work on IE 6.0</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-745'>JS2-745</a>] - File System Page Manager does not accept folders with dots</li>
+ </ul>
+ </subsection>
+ <subsection name="Improvement">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-584'>JS2-584</a>] - enable adding Velocity context objects without recompilation</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-672'>JS2-672</a>] - Add createProperty API to the Preferences Provider component</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-673'>JS2-673</a>] - Set sql.src.path value in the project.properties</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-680'>JS2-680</a>] - Folder configuration form at a page edit area</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-683'>JS2-683</a>] - Folder/Page customizer improvement</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-685'>JS2-685</a>] - Add functionality to AJAX API to information about users</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-695'>JS2-695</a>] - The Desktop does NOT support the no-action layouts</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-700'>JS2-700</a>] - Display loading in progress message from desktop</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-701'>JS2-701</a>] - Package and compress the Jetspeed Desktop Javascript</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-702'>JS2-702</a>] - Optimize desktop menu loading</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-707'>JS2-707</a>] - When creating a new user, give option to create inside a subsite</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-709'>JS2-709</a>] - Update to latest dependencies</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-711'>JS2-711</a>] - Support JSP decorators as well as Velocity </li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-712'>JS2-712</a>] - Create new servlet session upon login (configurable)</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-713'>JS2-713</a>] - Put a hard-limit on session time-out for portal sessions</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-721'>JS2-721</a>] - Ability to determine if a Menu Option has a default page or not</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-723'>JS2-723</a>] - Option to configure DB PSML from the installer</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-739'>JS2-739</a>] - Improve Algorithms for Resource Validation and Template Localization</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-740'>JS2-740</a>] - Allow overriding the default Spring assembly without having to modify it</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-741'>JS2-741</a>] - More GroovyPortlet demos using the new Portals Bridges GroovyPortlet</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-747'>JS2-747</a>] - A valve creating template pages when a user logs on first.</li>
+ </ul>
+ </subsection>
+ <subsection name="New Feature">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-317'>JS2-317</a>] - Virtual Portal Implementation</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-691'>JS2-691</a>] - Allow user to customize all his pages and portlets (in user home folder) at once</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-716'>JS2-716</a>] - PSML and XML Import / Export Admin Portlet</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-724'>JS2-724</a>] - Audit logs for administrative actions</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-728'>JS2-728</a>] - Provide a Portals Bridges common.PortletResourceURLFactory implementation for Jetspeed</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-729'>JS2-729</a>] - Preliminary Portlet API 2.0 ResourceURL support allowing full response control like for cookies and compressed output streams</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-732'>JS2-732</a>] - A GroovyPortlet demo using the new Portals Bridges GroovyPortlet </li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-743'>JS2-743</a>] - Maximize on Edit</li>
+ </ul>
+ </subsection>
+
+ </section>
+ </body>
+</document>
\ No newline at end of file
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.2.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.2.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.xml Tue Dec 2 00:53:22 2008
@@ -0,0 +1,188 @@
+<?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>Jetspeed-2 Release Notes</title>
+ <subtitle>Jetspeed-2 Release Notes</subtitle>
+ <authors>
+ <person name="Ate Douma" email="ate@douma.nu" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Release Notes - Jetspeed 2 - Version 2.1">
+ <p>
+ The list below outlines the issues that are addressed with release 2.1. For a full list of features, see the
+ <a href="features.html">features list</a>.
+ </p>
+ <subsection name="Bug">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-134'>JS2-134</a>] - Language Set not created from supported-locale</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-168'>JS2-168</a>] - capabilities test fails on hsql</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-204'>JS2-204</a>] - PLT.7.1.2 Portlet URL securit y not implemented and absolute URL rendering</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-226'>JS2-226</a>] - Page Aggregation using STRATEGY_PARALLEL severly broken</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-273'>JS2-273</a>] - Editing Page Layout works incorrectly</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-282'>JS2-282</a>] - Error when session expires and portlet window is maximized</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-315'>JS2-315</a>] - Premature access to portal can break access to portlets.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-316'>JS2-316</a>] - JSF Component javascript not being rendered</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-339'>JS2-339</a>] - Calls to preferences.store() trigger a warning about missing transaction in OJB</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-375'>JS2-375</a>] - Database scripts broken on Oracle 8i</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-405'>JS2-405</a>] - Logout Problem when running behind Apache with mod_jk</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-438'>JS2-438</a>] - Broken link on web site</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-439'>JS2-439</a>] - typo in SSO sites portlet</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-445'>JS2-445</a>] - Unable to build J2 - Failed to download, Missing version numbers</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-448'>JS2-448</a>] - Oracle installer broken.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-450'>JS2-450</a>] - portlet application manager eats useful exception message</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-452'>JS2-452</a>] - unable to add a custom mode to the portlet.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-456'>JS2-456</a>] - PageImporter did not import <users/> element in page.security to database</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-458'>JS2-458</a>] - J2 Security constraint is broken by DatabasePageManager</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-460'>JS2-460</a>] - Minimize/Restore broken</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-464'>JS2-464</a>] - Redeployment of portlets that have services defined jetspeed-portlet.xml ARE NOT updating the JETSPEED_SERVICES table with new/altered values.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-467'>JS2-467</a>] - Broken links in http://portals.apache.org/jetspeed-2/getting-started-binary.html</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-468'>JS2-468</a>] - Customizer cannot edit nested layouts.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-473'>JS2-473</a>] - Many uses of Fragment.getFragments() assume access to the underlying list, not a copy: this is invalid</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-475'>JS2-475</a>] - Proposed changes in portal permissions</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-478'>JS2-478</a>] - admin portlets application inconsistency</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-479'>JS2-479</a>] - Non-thread safe code in the DB PageManager</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-481'>JS2-481</a>] - Unable to change Jetspeed2's default theme "tigris" to another one.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-483'>JS2-483</a>] - buggy css layouts / patch for table based layout</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-485'>JS2-485</a>] - admin portlets profiler admin</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-495'>JS2-495</a>] - OJB + Spring Transactions broken</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-496'>JS2-496</a>] - J2 on tomcat 5.5.15: 403 returned to client browser when any user that doesn't have admin role attempts to log in</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-497'>JS2-497</a>] - Can not correctly display the display-names of layout-portlet when editing a page in Chinese or Japanese.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-498'>JS2-498</a>] - When editting page, can not correctly display the display-name in the language, which have country name.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-501'>JS2-501</a>] - Pluto ObjectID implementation produces invalid map key values</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-503'>JS2-503</a>] - UserManager's setUserEnabled() method fails after creating new users</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-509'>JS2-509</a>] - Portlet Preferences are not stored on a user by user basis</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-511'>JS2-511</a>] - org.apache.jetspeed.om.portlet.impl.PortletDefinitionImpl line 558 throws NPE</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-518'>JS2-518</a>] - Setting PorletPreferences in PSML does not work</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-519'>JS2-519</a>] - Concurrency issues due to ServletPortletInvoker being used as singleton</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-520'>JS2-520</a>] - RSSPortlet ignores preference itemdisplayed</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-522'>JS2-522</a>] - Infinite loop created in PortletWindowAccessorImpl.getWindowFromCache() while under load</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-526'>JS2-526</a>] - JBoss web.xml entry for security-constraint login/redirector wont work under Tomcat</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-528'>JS2-528</a>] - Error while trying to deploy portlets</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-530'>JS2-530</a>] - MenuElementImpl.getMetadata does not return the defined data</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-535'>JS2-535</a>] - SSO default resources</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-556'>JS2-556</a>] - decorator.vm in portlet decorators not overriden</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-562'>JS2-562</a>] - LDAP attribute name comparison should be case-insensitive</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-564'>JS2-564</a>] - wrong italian localization strings</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-571'>JS2-571</a>] - Changes to page structure (PSML) using the DatabasePageManager are not reflected to the internal page representation.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-572'>JS2-572</a>] - Maven 2 build requires spring-portlet and spring-beans version</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-576'>JS2-576</a>] - PortletDefinitionImpl.getDisplayNameSet() returns empty set if getDisplayName() is not called first</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-582'>JS2-582</a>] - Portlet sessions are not invalidated when the portal session is destroyed with emptySessionPath="true"</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-588'>JS2-588</a>] - "Portal Site Detail" portlet doesn't work in trunk</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-590'>JS2-590</a>] - Moving / Deleting portlets doesn't always work under DatabasePageManager</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-591'>JS2-591</a>] - cannot access a new page with a multibyte page name</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-592'>JS2-592</a>] - The customizer portlet cannot add portlets to a .psml page when logged in as admin</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-599'>JS2-599</a>] - Statistics throw a NumberFormatException for last 24 hours and last 7 days</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-605'>JS2-605</a>] - Query string parameters should not (by default) be provided to portlets to be compliant to JSR 168 spec requirements</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-607'>JS2-607</a>] - An error occur when trying storing a null value in preferences</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-611'>JS2-611</a>] - Custom Portlet Mode and Window State incorrectly handled / processed from portlet.xml</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-613'>JS2-613</a>] - ConcurrentModificationException under high load</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-633'>JS2-633</a>] - nested layout broken with permission security enabled</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-635'>JS2-635</a>] - count of portlet on portlet selecotor</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-641'>JS2-641</a>] - override.properties isn't loaded by the bean 'placeholderConfig'</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-646'>JS2-646</a>] - ActionValveImpl can throw NullPointerException under clustered environment.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-651'>JS2-651</a>] - Add Portlet fails when logged in as Subsite User</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-652'>JS2-652</a>] - Desktop does not render page if any portlet on the page shows "Failed to retrieve Portlet Definition"</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-655'>JS2-655</a>] - Entity Editor Broken</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-656'>JS2-656</a>] - Cross-Site Scripting (XSS) vulnerability</li>
+ </ul>
+ </subsection>
+ <subsection name="Improvement">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-110'>JS2-110</a>] - Replace HSQL with Axion as default database in J2</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-190'>JS2-190</a>] - Changing the portlet.xml in a deployed portlet/webapp does not change Jetspeed.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-198'>JS2-198</a>] - Portlets don't use user-specific preferences. The Portlet Preferences for anon user are always used.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-264'>JS2-264</a>] - Updating just the portlet content</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-329'>JS2-329</a>] - 3 new 100% table-free portlet decorations.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-354'>JS2-354</a>] - Provision for portlet-level permissions</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-449'>JS2-449</a>] - User Specific Preferences</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-461'>JS2-461</a>] - Serializer component</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-462'>JS2-462</a>] - Need to clean up Velocity logs, too many warnings and some errors even</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-470'>JS2-470</a>] - LDAP Authorization Support Implementation + Sun LDAP Authentication Support</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-480'>JS2-480</a>] - Statistics cleanup</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-491'>JS2-491</a>] - Enhance J2 LDAP Security Documentation</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-493'>JS2-493</a>] - More chinese Localization</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-504'>JS2-504</a>] - update chinese Localization</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-506'>JS2-506</a>] - Extend profiler to fallback to parent folders when requested path is not available.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-508'>JS2-508</a>] - Fixing commons-logging on WebSphere and other application servers</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-516'>JS2-516</a>] - Make selection of last visited page in folder on folder request optional</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-527'>JS2-527</a>] - Allow email addresses to be used for user accounts by making hierarchical interpretation of principal names optional</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-534'>JS2-534</a>] - Korean translation for portal, portal-site, j2-admin, demo, rss, gems, layout-portlets, and jetspeed-api.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-539'>JS2-539</a>] - Korean translation for *.psml, *.link, and folder.metadata files under the /WEB-INF/pages/**/ folder.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-541'>JS2-541</a>] - Log initialization failures when deploying on Websphere 6.0.2.x</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-543'>JS2-543</a>] - Velocity logging using the jetspeed-webapp-logging component</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-549'>JS2-549</a>] - Simple documentation for using the JSF bridge in Jetspeed</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-568'>JS2-568</a>] - Upgrade commons-httpclient bundled in jetspeed war</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-575'>JS2-575</a>] - Sun LDAP connection pooling implementation needed so that Jetspeed does not need to be restarted if LDAP server is restarted or connection is lost.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-578'>JS2-578</a>] - Improve Creation of PSML pages for new users</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-600'>JS2-600</a>] - update Chinese Localization</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-603'>JS2-603</a>] - Upgrade Search component to lucene 2.0.0</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-606'>JS2-606</a>] - Allow deployment of local portlet applications without a jetspeed- name prefix</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-614'>JS2-614</a>] - Jetspeed Deploy compliant with servlet spec 2.4</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-640'>JS2-640</a>] - Run with active Java security manager enabled</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-642'>JS2-642</a>] - update chinese LOCALIZATION</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-648'>JS2-648</a>] - A multi-database profile settings for maven 2</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-649'>JS2-649</a>] - XML Schemas for Jetspeed XML Data</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-654'>JS2-654</a>] - enhance components to use JetspeedCache for distributed environments</li>
+ </ul>
+ </subsection>
+ <subsection name="New Feature">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-275'>JS2-275</a>] - Option to make Action URLs relative or absolute</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-283'>JS2-283</a>] - Basic Ajax Service Implementation</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-466'>JS2-466</a>] - Production Configuration / Hardcode Base URL</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-476'>JS2-476</a>] - Create user pages from a user's roles</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-490'>JS2-490</a>] - A profiler rule which serves content based on the network associated with the http request</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-514'>JS2-514</a>] - Jetspeed Desktop</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-523'>JS2-523</a>] - Supporting custom PortletModes and WindowStates</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-524'>JS2-524</a>] - Providing a "print" custom PortletMode and a "solo" custom WindowState</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-550'>JS2-550</a>] - A new Two-way password encoding service allowing decoding of encoded passwords</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-557'>JS2-557</a>] - Property Loader Valve</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-559'>JS2-559</a>] - Place portlets in decorators</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-583'>JS2-583</a>] - Message properties files in greek</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-585'>JS2-585</a>] - A continuous build script</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-596'>JS2-596</a>] - CLONE -Support Tomcat TCP Clustering</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-610'>JS2-610</a>] - Categorization of Portlets with new Category Portlet Selector</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-644'>JS2-644</a>] - Remote Portlet Application Deployer</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-645'>JS2-645</a>] - Portlet Security Constraints</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-647'>JS2-647</a>] - Cluster Deployment</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-653'>JS2-653</a>] - Show theme depending what user you are</li>
+ </ul>
+ </subsection>
+ <subsection name="Task">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-361'>JS2-361</a>] - Portlet Caching implemented in Aggregator</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-366'>JS2-366</a>] - Clean up orphan tables in J2 DB schema</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-529'>JS2-529</a>] - Minimize verbose debugging output of Missing/Forbidden page fallback in PortalSiteSessionContextImpl</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-570'>JS2-570</a>] - Add Support for SpringMVC Portlet framework plus doHeader phase</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-573'>JS2-573</a>] - Profiler docs</li>
+ </ul>
+ </subsection>
+ <subsection name="Wish">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-344'>JS2-344</a>] - PHP 5 support</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-521'>JS2-521</a>] - j2-admin: Styling of login error messages (Login.jsp)</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-554'>JS2-554</a>] - Upload Jetspeed jars to Ibiblio</li>
+ </ul>
+ </subsection>
+
+
+ </section>
+ </body>
+</document>
\ No newline at end of file
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes-2.1.xml
------------------------------------------------------------------------------
svn:keywords = Id
Added: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes.xml
URL: http://svn.apache.org/viewvc/portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes.xml?rev=722405&view=auto
==============================================================================
--- portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes.xml (added)
+++ portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes.xml Tue Dec 2 00:53:22 2008
@@ -0,0 +1,120 @@
+<?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>Jetspeed-2 Release Notes</title>
+ <subtitle>Jetspeed-2 Release Notes</subtitle>
+ <authors>
+ <person name="Ate Douma" email="ate@douma.nu" />
+ </authors>
+ </properties>
+ <body>
+ <section name="Release Notes - Jetspeed 2 - Version 2.1.3">
+ <p>
+ The list below outlines the issues that are addressed with release 2.1.3 For a full list of features, see the
+ <a href="features.html">features list</a>.
+ </p>
+ <p>
+ And the release notes of the previous release 2.1.2 are available here: <a href="release-notes-2.1.2.html">release notes 2.1.2</a>.
+ </p>
+ <subsection name="Bug">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-593'>JS2-593</a>] - NullPointerException whent getting database connection in BatchedStatistics</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-612'>JS2-612</a>] - Get NullPointerException around pageManager in FolderImpl under high load</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-666'>JS2-666</a>] - Clustered Environment: constraint violation if clones are started at the same time</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-750'>JS2-750</a>] - LDAP login not resolving DN correctly</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-752'>JS2-752</a>] - Desktop pipeline: drag and drop and portlet relocation</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-753'>JS2-753</a>] - Desktop Pipeline: sticky mouse pointer after portlet was resized in Untiled mode.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-754'>JS2-754</a>] - Desktop Pipeline: javascript error when click on 'Aditional Link'</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-756'>JS2-756</a>] - Desktop Pipeline: Browser Refresh Issue After Page Edit</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-757'>JS2-757</a>] - Removing /_user/guest folder gives edit access to all pages</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-758'>JS2-758</a>] - Ukrainian symbols doesn't save through Portal Site Manager</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-759'>JS2-759</a>] - Jetspeed caches content of portal pages unexpectedly</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-762'>JS2-762</a>] - Cannot return to view mode after changing to simple layout theme in page edit mode.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-764'>JS2-764</a>] - There are much DOCTYPE directives in every result page of portal </li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-767'>JS2-767</a>] - Portlet Action not working when using JetspeedPowerTool</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-768'>JS2-768</a>] - Desktop pipeline gets null page in request context</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-769'>JS2-769</a>] - Layout Portlets do not support content types other than text/html</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-784'>JS2-784</a>] - Adding portlet doesn't work in 2.1.3 trunk!</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-790'>JS2-790</a>] - Many bugs in portal site manager portlet</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-795'>JS2-795</a>] - Deadlock while release session on Websphere Release 6.0.2.19</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-796'>JS2-796</a>] - VelocityTwoColumns mentioned twice in layouts guide</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-798'>JS2-798</a>] - Portlet Selector fails on Safari browser</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-799'>JS2-799</a>] - Jetspeed cannot deploy portlet applications that run from the "/" context.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-800'>JS2-800</a>] - Memeory Leak Caused by org.apache.jetspeed.container.window.impl.PortletWindowAccessorImpl</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-802'>JS2-802</a>] - Eclipse m2.classpath has some typos</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-803'>JS2-803</a>] - Java6 can't compile Jetspeed</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-807'>JS2-807</a>] - Attached files gives you the ability to run the tests under Maven-2 (currently broken)</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-810'>JS2-810</a>] - Rule criteria is not ordered correctly</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-814'>JS2-814</a>] - Ldap User DN is incorrectly calculated when search filterBase is empty</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-815'>JS2-815</a>] - SSOIframePortlet doesn't save changed remote principal name</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-816'>JS2-816</a>] - Jetspeed common javascript doesn't support running the portal under ROOT context</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-819'>JS2-819</a>] - Edit mode of Category Portlet Selector doesn't work on IE browser.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-820'>JS2-820</a>] - display UNICODE in desktop mode.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-822'>JS2-822</a>] - Flash Portlets are broken on Desktop</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-824'>JS2-824</a>] - Odd behavior on maximize and minimize of portlets under Desktop, IE6 only</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-826'>JS2-826</a>] - Invalid DN values in group/role member attributes result in null pointer dereferences in the BasePrincipalImpl class</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-827'>JS2-827</a>] - Does't work that uploading files in desktop mode using "multipart/form-data"</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-829'>JS2-829</a>] - Issue with PersistenceBrokerPreferencesProvider.resolveChildren() when cached preferences are evicted.</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-830'>JS2-830</a>] - Unpredictable exceptions due to unsynchronized HashMap in AbstractProfilingRul</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-833'>JS2-833</a>] - associations between portal and remote principal are not removed</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-836'>JS2-836</a>] - Lookup of LDAP users per role using a role membership attribute on a user is broken</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-837'>JS2-837</a>] - Attributes template for initial LDAP user/role/group attributes does not accept '=' sign</li>
+ </ul>
+ </subsection>
+ <subsection name="Improvement">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-710'>JS2-710</a>] - Dynamically Hide Portlets at request time</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-755'>JS2-755</a>] - Desktop Pipeline: Blank deley when switch page</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-779'>JS2-779</a>] - Supporting Pocket PC</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-780'>JS2-780</a>] - Provide out-of-the-box Wicket portlet support</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-785'>JS2-785</a>] - Parallel Rendering on Websphere 6.1</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-787'>JS2-787</a>] - Non-informative error handling in PortalSiteManager. I've created a patch</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-788'>JS2-788</a>] - Localize File Portlet resources</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-789'>JS2-789</a>] - Login without posting all credentials via HTTP request</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-793'>JS2-793</a>] - Support deployment of jetspeed under a custom context name (e.g. ROOT) with the maven 1 jetspeed plugin</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-797'>JS2-797</a>] - Improve LDAP implementation and documentation for Apache DS 1.0.2</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-805'>JS2-805</a>] - Improve Credentials Password Support</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-806'>JS2-806</a>] - Portlets should return to normal view state on click of menu navigation from portal</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-808'>JS2-808</a>] - Maximize on edit-defaults option</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-812'>JS2-812</a>] - Better support for MSSQL</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-821'>JS2-821</a>] - CategoryPortletSelector no portlets displayed in IE6 / Update CategoryPortletSelector localization Korean</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-823'>JS2-823</a>] - NoAction Layouts under desktop pipeline behave different from portal pipeline</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-835'>JS2-835</a>] - Improve Permissions and Constraints Admin portlets to support the latest Portlet Modes</li>
+ </ul>
+ </subsection>
+ <subsection name="New Feature">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-634'>JS2-634</a>] - edit_defaults custom portlet mode</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-708'>JS2-708</a>] - Ant Custom Build Tutorial</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-716'>JS2-716</a>] - PSML and XML Import / Export Admin Portlet</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-729'>JS2-729</a>] - Preliminary Portlet API 2.0 ResourceURL support allowing full response control like for cookies and compressed output streams</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-791'>JS2-791</a>] - configure the security constraint on a particular portlet fragment using new custom config portlet mode</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-809'>JS2-809</a>] - Add table schema aware datasource proxy</li>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-834'>JS2-834</a>] - Automatically cleanup of the PortalURL: no navigational state in browser url</li>
+ </ul>
+ </subsection>
+ <subsection name="Wish">
+ <ul>
+ <li>[<a href='https://issues.apache.org/jira/browse/JS2-786'>JS2-786</a>] - Tool for conversion preferences from database no-principal preferences to defaults preferences in psml pages</li>
+ </ul>
+ </subsection>
+
+ </section>
+ </body>
+</document>
\ No newline at end of file
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes.xml
------------------------------------------------------------------------------
svn:eol-style = native
Propchange: portals/jetspeed-2/portal/branches/JS2-871-pluto-2.0-upgrade/src/site/xdoc/release-notes.xml
------------------------------------------------------------------------------
svn:keywords = Id
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
|