[
https://jira.codehaus.org/browse/MWAR-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MWAR-314.
------------------------------------
Resolution: Not A Bug
Assignee: Karl-Heinz Marbaise
If you set {{failOnMissingWebXml}} to {{false}} you say that you don't like to
break your build if your {{web.xml}} does not exist, or is not readable etc.
which is your described scenario to set {{webXml}} to {{WhatEver}}.
Furthermore if you comment out {{webXml}} you say you don't define web.xml at
all and the build succeeded which is based on setting {{failOnMissingWebXml}}
to {{false}} correct.
So from my site of view i will close this issue as not a bug. If you have any
objections don't hesitate to reopen the issue.
> failOnMissingWebXml ignored when webXml set
> -------------------------------------------
>
> Key: MWAR-314
> URL: https://jira.codehaus.org/browse/MWAR-314
> Project: Maven WAR Plugin
> Issue Type: Bug
> Affects Versions: 2.4
> Environment: Windows 7, IBM RAD 9.0
> Reporter: Jakob Galbavy
> Assignee: Karl-Heinz Marbaise
> Priority: Minor
> Attachments: pom.xml
>
>
> Hi,
> if the webXml attribute is set in the configuration of the plugin (in my case
> inherited from a parent pom), the failIOnMissingWebXml boolean is ignored.
> To reproduce that:
> * import maven project from attached pom OR create new project (simple
> archetype), package: war
> * use attached pom.xml OR include the plugin in the pom and set webXml to
> something and failOnMissingWebXml to false
> * mvn clean install
> -> failed
> ********
> * comment the webXml attribute out
> * mvn clean install
> -> success
> cheers
> Jakob
> PS: in my understanding of xml, using <webXml /> in the pom should set that
> attribute to NULL, but that doesn't work either. Is that another bug or
> supposed to be like that?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
