[jira] Commented: (MWAR-168) "Dependency Has Changed" Incorrectly Reported

["Dmitry Katsubo (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MWAR-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203471#action_203471 ] 

Dmitry Katsubo commented on MWAR-168:
-------------------------------------

I have the warning messages of the same nature:
{code}
[INFO] Dependency[Dependency {groupId=commons-logging, artifactId=commons-logging, version=1.1.1, type=jar}] has changed (was Dependency {groupId=commons-logging, artifactId=commons-logging, version=1.1.1, type=jar}).
[INFO] Dependency[Dependency {groupId=commons-lang, artifactId=commons-lang, version=2.4, type=jar}] has changed (was Dependency {groupId=commons-lang, artifactId=commons-lang, version=2.4, type=jar}).
{code}

maven-war-plugin 2.1-alpha-2
maven-jar-plugin 2.2

The warning message appears for the dependences, which have versions substantiated by a variable, for example in parent pom:

{code}
<properties>
	<commons.logging.version>1.1.1</commons.logging.version>
	<commons.lang.version>2.4</commons.lang.version>
</properties>
{code}

in module pom:

{code}
<dependency>
	<groupId>commons-logging</groupId>
	<artifactId>commons-logging</artifactId>
	<version>${commons.logging.version}</version>
</dependency>
<dependency>
	<groupId>commons-lang</groupId>
	<artifactId>commons-lang</artifactId>
	<version>${commons.lang.version}</version>
</dependency>
{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