use-latest-snapshots does not respect -DallowIncrementalUpdates=false
---------------------------------------------------------------------
Key: MVERSIONS-170
URL: https://jira.codehaus.org/browse/MVERSIONS-170
Project: Maven 2.x Versions Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Apache Maven 3.0.3 (r1075438; 2011-03-01 01:31:09+0800)
Maven home: /usr/share/maven
Java version: 1.6.0_29, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7.2", arch: "x86_64", family: "mac"
Reporter: Honnix Liang
I have a few branches in my project A, and thus a few different versions of
artifacts, say they're:
1.0.0
1.0.0-pc1-SNAPSHOT
1.0.0-pc2-SNAPSHOT
1.0.0-pc3-SNAPSHOT
1.0.1-SNAPSHOT
And another project B depends on A.
Consider following situation:
B depends on A:1.0.0, and now I need to make it depend on A:1.0.0-pc3-SNAPSHOT.
> mvn versions:use-latest-snapshots -DallowIncrementalUpdates=false
But after this, the dependency version is changed to 1.0.1-SNAPSHOT, it does
not respect my configuration.
If running with "-X", I can get following debug output:
[INFO] Upper bound: 1.0.1
[DEBUG] Candidate versions [1.0.0-pc1-SNAPSHOT, 1.0.0-pc2-SNAPSHOT,
1.0.0-pc3-SNAPSHOT, 1.0.1-SNAPSHOT]
[INFO] Updated com.honnix.maven.version:version-platform:jar:null:1.0.0 to
version 1.0.1-SNAPSHOT
I can fully understand why Upper bound is set to 1.0.1, but after getting a few
candidates, at least, it should filter out according to my configuration, and
in this case, 1.0.1-SNAPSHOT should be excluded, and I should have got
1.0.0-pc3-SNAPSHOT.
--
This message is automatically generated by JIRA.
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
