You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Elliot Metsger (JIRA)" <ji...@apache.org> on 2007/06/05 01:50:27 UTC
[jira] Updated: (PLUTO-378) Pluto requires custom entries in
web.xml whcih prevents the deployment of JSR 168 portlest
[ 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: 1.1.4
1.2.0
> 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, 1.1.4
>
>
> 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.