You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephane Nicoll (JIRA)" <ji...@codehaus.org> on 2010/08/16 08:38:32 UTC
[jira] Updated: (MWAR-168) "Dependency Has Changed" Incorrectly
Reported
[ http://jira.codehaus.org/browse/MWAR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephane Nicoll updated MWAR-168:
---------------------------------
Description:
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.
was:
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.
Fix Version/s: 2.2
> "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
> Fix For: 2.2
>
>
> 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