[
https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Nicklous resolved PLUTO-378.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
v3 no longer requires a deployment descriptor
> Pluto requires custom entries in web.xml whcih prevents the deployment of JSR
> 168 portlest
> ------------------------------------------------------------------------------------------
>
> Key: PLUTO-378
> URL: https://issues.apache.org/jira/browse/PLUTO-378
> Project: Pluto
> Issue Type: Wish
> Components: portlet container
> Reporter: Stephane Nicoll
> Priority: Minor
> Fix For: 3.0.0
>
>
> According to the documentation, pluto requires any war containing portlets to
> be updated by a plugin in order to allow a deployment in pluto, see
> http://portals.apache.org/pluto/v11/deploying.html
> This is a show stopper for people working with several portlets container
> since the stuff that needs to be added makes a deployment into another portal
> system impossible. Pluto should inject the necessary stuff on the fly instead
> (just like Liferay does for instance).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
