[
https://issues.apache.org/jira/browse/PLUTO-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Nicklous resolved PLUTO-576.
----------------------------------
Resolution: Fixed
Fix Version/s: 3.0.0
v3 no longer requires a web.xml file.
> Maven pluto plugin should fail or generate warning if web.xml already
> contains servlet/servlet-mapping similar to one being added by maven pluto
> plugin
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: PLUTO-576
> URL: https://issues.apache.org/jira/browse/PLUTO-576
> Project: Pluto
> Issue Type: Improvement
> Components: maven pluto plugin
> Reporter: Gary Weaver
> Fix For: 3.0.0
>
>
> If the web.xml that the plugin is altering already contains a servlet and/or
> servlet-mapping element that looks very much like the ones it is adding it
> should either fail or at least generate a warning. I know that having the
> pluto-generated config in the web.xml of the portlet to be "plutofied" by the
> plugin is wrong, but if the plugin makes web.xml invalid because that info
> already exists, it seems like it should check for it. Please ignore this if
> it is an invalid request, but I remembered that it worked this way, it caused
> problems for at least a few people developing portlets for uPortal over the
> past 2 years reported on the JASIG uportal-user/portlet-dev lists, and Eric
> Dalquist just mentioned that perhaps this would be a good place to mention it
> also since uPortal now uses this plugin. Thanks, guys!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
