[
http://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226897#action_226897
]
Mark Derricutt commented on MNG-3092:
-------------------------------------
After getting Maven 3 running again I retried our builds at $work with it, I
did like the lack of -SNAPSHOTs being resolved for working with individual
artifacts as it drove me to actually release some long standing 'test support'
artifacts. And I see a good upside of this would be much more regular
releasing of artifacts across the board.
However, when it came to running our integration tests, which use the
maven-dependency-plugin to copy all of our projects artifacts (listed as test
dependencies) to the target directory, and deploy them into an OSGi container,
it was apparent that we'd have to drop the use of version ranges and modify the
test projects dependencies EVERY TIME one of the projects artifacts changed, as
the ranges no longer resolve -SNAPSHOTs.
If this change is going to go ahead and stay in maven 3 - is there an
alterative way of doing the above, where an integration build wants to pull in
all available SNAPSHOT releases.
Ideally, I'd love to see this new behavior the default in Maven 3, but with an
override setting to add into the maven-dependency-plugin or somewhere to allow
for SNAPSHOTs.
Mark
> Version ranges with non-snapshot bounds can contain snapshot versions
> ---------------------------------------------------------------------
>
> Key: MNG-3092
> URL: http://jira.codehaus.org/browse/MNG-3092
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Reporter: Mark Hobson
> Assignee: Mark Hobson
> Fix For: 3.0-beta-1
>
> Attachments: MNG-3092.patch
>
>
> Contrary to the 2.0 design docs:
> "Resolution of dependency ranges should not resolve to a snapshot
> (development version) unless it is included as an explicit boundary."
> -- from
> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification
> The following is equates to true:
> VersionRange.createFromVersionSpec( "[1.0,1.1]" ).containsVersion( new
> DefaultArtifactVersion( "1.1-SNAPSHOT" ) )
> The attached patch only allows snapshot versions to be contained in a range
> if they are equal to one of the boundaries. Note that this is a strict
> equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT.
--
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
