[ http://jira.codehaus.org/browse/MRELEASE-134?page=comments#action_68480 ]
Akbarr commented on MRELEASE-134: --------------------------------- This document: http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges addressed the requirements for version ranges and stated that "Resolution of dependency ranges should not resolve to a snapshot (development version) unless it is included as an explicit boundary". I think this requirement was forgetten when version ranges were implemented. > Release prepare fails with version ranges > ----------------------------------------- > > Key: MRELEASE-134 > URL: http://jira.codehaus.org/browse/MRELEASE-134 > Project: Maven 2.x Release Plugin > Type: Bug > Versions: 2.0-beta-4 > Reporter: Mike Perham > > > {code} > <version>[1.1.0,)</version> > {code} > This version range can resolve to the latest dev SNAPSHOT which causes the > release plugin to fail due to a SNAPSHOT dependency. The release plugin > should check that the original version specification includes a non-SNAPSHOT > version (1.1.0) and so can be released without harm. -- 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
