[
https://issues.apache.org/jira/browse/PLUTO-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliot Metsger updated PLUTO-378:
---------------------------------
Fix Version/s: (was: 1.1.4)
This fix won't get into 1.1.4, and it may not get into the 1.1.x branch because
its implementation may require changing interfaces which would break binary
compatibility with past 1.1.x releases.
A thread has started on pluto-dev and is being fleshed out on general@ as to
whether or not Pluto is the appropriate place for this code.
http://www.nabble.com/hot-deploy---auto-assembly-design-tf4041191.html
http://www.nabble.com/forum/ViewPost.jtp?post=11492057&framed=y
> 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: Bug
> Components: portlet container
> Affects Versions: 1.1.3
> Reporter: Stephane Nicoll
> Assignee: Elliot Metsger
> Priority: Critical
> 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.
