[mojo-dev] [jira] (MVERSIONS-204) Bug with import scoped entry in dependency management

Thu, 27 Dec 2012 02:20:13 -0800

Issue Type: Bug Bug
Affects Versions: 2.0, 1.2
Assignee: Unassigned
Created: 27/Dec/12 4:19 AM
Description:

In my project's pom.xml I have a dependency management like this:

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>mycompany.groupid</groupId>
            <artifactId>artifactName</artifactId>
            <version>4.0-SNAPSHOT</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>


When I run "mvn versions:use-latest-versions" it did not replace the version.



I added this in my dependancy management:




<dependency>
    <groupId>mycompany.groupid</groupId>
    <artifactId>artifactName-child1</artifactId>
    <version>4.0-SNAPSHOT</version>
</dependency>





('artifactName' is the parent of 'artifactName-child1'. The packaging of 'artifactName-child1' is jar and the packaging of 'artifactName' is pom)



Then I ran again the command, and the version of 'artifactName-child1' was correctly updated.

So it seems that the import scoped entry was ignored by the plugin.



I also tried the solution given in this StackOverflow post but it did not work.



Regards
Environment: apache-maven-3.0.3
windows 7
java 1.7.0_09
Project: Maven 2.x Versions Plugin
Priority: Major Major
Reporter: Benoit Brouard
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to