You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alex lewis (Jira)" <ji...@apache.org> on 2019/11/16 08:08:00 UTC
[jira] [Commented] (MWAR-428) Clean required when dependencies are
updated
[ https://issues.apache.org/jira/browse/MWAR-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975629#comment-16975629 ]
Alex lewis commented on MWAR-428:
---------------------------------
This is a duplicate of MWAR-427
> Clean required when dependencies are updated
> --------------------------------------------
>
> Key: MWAR-428
> URL: https://issues.apache.org/jira/browse/MWAR-428
> Project: Maven WAR Plugin
> Issue Type: Bug
> Affects Versions: 3.2.3
> Reporter: Alex lewis
> Priority: Major
>
> A {{mvn clean}} is required when a dependency version is updated in a war project pom file; otherwise, both the old and new version of the dependency will appear in the lib directory of the war.
> Steps to recreate:
> # Create simple war project with 1 or more dependencies.
> # {{mvn clean package}}
> # List library jar files in {{target/<war>/lib}}.
> # Update a dependency version in pom.xml
> # {{mvn package}} (note: no {{clean}}).
> # List library jar files in {{target/<war>/lib}}.
> ** At this point the lib folder will contain both versions of the dependency.
> Expected:
> A {{clean}} should not required when dependency versions are updated; {{mvn package}} should be sufficient. This expectation is somewhat driven by a discussion with [~rfscholte] on twitter.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)