Adrian Muraru created MNG-5228:
----------------------------------
Summary: [regression] Local snapshots are ignored when version
range is specified in dep
Key: MNG-5228
URL: https://jira.codehaus.org/browse/MNG-5228
Project: Maven 2 & 3
Issue Type: Bug
Environment: $ mvn -v
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /opt/MAVEN/current
Java version: 1.7.0_02, vendor: Oracle Corporation
Java home: /opt/JAVA/jdk1.7.0_02/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.0.0-14-generic", arch: "amd64", family: "unix"
Reporter: Adrian Muraru
a) "mvn deploy" libA (deploy version libA, 1.0.0 in remote repository)
b) wait a few seconds
c) "mvn install" libA, this creates a local snapshot that is newer than the
latest release version in remote repo (libA, 1.0.0-SNAPSHOT)
d) in a dependent project libB, specifying dependency on libA as
[1.0.0-SNAPSHOT, 1.0.1) "mvn compile -U"
Latest released version in remote repo is always used and local SNAPSHOT never
used (although newer and included in version range)
Related to MNG-4955 ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira