[
http://jira.codehaus.org/browse/MWAR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195116#action_195116
]
Stevo Slavic commented on MWAR-168:
-----------------------------------
This seems to be fixed in current 2.1-beta-1. To use it one should specify the
version in project's plugin settings:
{code}
...
<build>
...
<pluginManagement>
<plugins>
...
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1-beta-1</version>
</plugin>
...
</plugins>
</pluginManagement>
...
</build>
...
{code}
> "Dependency Has Changed" Incorrectly Reported
> ---------------------------------------------
>
> Key: MWAR-168
> URL: http://jira.codehaus.org/browse/MWAR-168
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
> Affects Versions: 2.1-alpha-2
> Reporter: gotama
> Assignee: Stephane Nicoll
>
> In maven-war-plugin 2.1-alpha-2, execute the following on a war project:
> mvn clean;
> mvn install;
> mvn install;
> The 3rd command incorrectly lists messages for each dependency as follows:
> [INFO] Dependency[Dependency {groupId=com.mycompany, artifactId=myartifact,
> version=8.6.1, type=jar}]
> has changed (was Dependency {groupId=com.mycompany, artifactId=myartifact,
> version=8.6.1, type=jar}).
> The first time that mvn install is run, dependencies are added to:
> target\myapp-war-1.1-SNAPSHOT\WEB-INF\lib
> The second invocation of mvn install appears to fail in comparing the
> existing jars in the above path with what is in the repository. The message
> states the dependencies have changed when in fact they have not.
> This problem does not exist in maven-war-plugin 2.0.2.
--
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
