[
http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111718
]
Stephane Nicoll commented on MWAR-120:
--
Oh I see. This check is kinda historical actually, I just need to check
whether
[
http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111719
]
Stephane Nicoll commented on MWAR-120:
--
Okay, reproduced.
Note that I have a slightly different behavior in testing harne
[
http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_77
]
Aaron Digulla commented on MWAR-120:
I think I found it: In the code, you check whether the option is set. If so,
you add
[
http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108422
]
Stephane Nicoll commented on MWAR-120:
--
No that's ok. I can have a look.
> Option containerConfigXML doesn't work
> -
[
http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108362
]
Aaron Digulla commented on MWAR-120:
Maybe this is a regression because of an update of plexus? I tried to
plexus-utils 1.
[
http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108306
]
Stephane Nicoll commented on MWAR-120:
--
Funny. I guess it has something to do with the way plexus build the archive.
Than
[
http://jira.codehaus.org/browse/MWAR-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108226
]
Aaron Digulla commented on MWAR-120:
The affected version is 2.0.2.
What puzzles me is the log output of maven:
{code}
>
