[
http://jira.codehaus.org/browse/MWAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephane Nicoll updated MWAR-118:
---------------------------------
Issue Type: Wish (was: Bug)
the usual way to deal with this is by calling clean even if I agree it should
be handled nicely by Maven.
> jar in lib dir are not cleaned if version of the changes im pom.xml
> -------------------------------------------------------------------
>
> Key: MWAR-118
> URL: http://jira.codehaus.org/browse/MWAR-118
> Project: Maven 2.x War Plugin
> Issue Type: Wish
> Affects Versions: 2.0.2
> Reporter: Dominique Jean-Prost
>
> In a pom war, if you change the version of a jar with compile or runtime
> scope, previous jar is not cleaned in target/lib dir. You can then get 2
> version of the same jar : one for the actual version of the pom, one for the
> previous version of the pom.
> Packaging should check if what is in target dir is ok with the pom.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
