[
https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma updated PLUTO-378:
----------------------------
Priority: Minor (was: Critical)
Affects Version/s: (was: 1.1.3)
Issue Type: Wish (was: Bug)
Downgrading this old issue to a Minor Wish.
*if* this is ever going to be provided for Pluto, then probably as a common
functionality shared with Jetspeed-2 (which has this already).
There is nothing planned to do so though right now.
> 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
> Assignee: Elliot Metsger
> Priority: Minor
> Fix For: 1.2.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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
