maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephane Nicoll (JIRA)" <>
Subject [jira] Commented: (MWAR-168) "Dependency Has Changed" Incorrectly Reported
Date Thu, 04 Sep 2008 08:12:48 GMT


Stephane Nicoll commented on MWAR-168:

this is a new feature and this is a "known" problem but thanks for the bug hunting which will
help fixing it :)

You can safely ignore it (or you can disable the cache to avoid the message)

> "Dependency Has Changed" Incorrectly Reported
> ---------------------------------------------
>                 Key: MWAR-168
>                 URL:
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1-alpha-2
>            Reporter: gotama
> 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,
> has changed (was Dependency {groupId=com.mycompany, artifactId=myartifact, version=8.6.1,
> 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:
For more information on JIRA, see:


View raw message