[
https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322945#comment-322945
]
Scott Sosna commented on MNG-3092:
----------------------------------
@Sergei
I realize there's a new dependency management library, I also know it flat-out
does not perform, and from aether's introduction there were problems. From
what I can tell, it was prematurely introduced, some bugs have been fixed, but
performance with ranges bites. I don't agree about Maven2, I heavily rely on
version ranges with SNAPSHOTs and have no problems, whereas Maven3 is
absolutely unusable in its current form. Sure, it appears that reverting to
Maven2 is going to be a lot of work, but fixing Maven3 might be more. Don't
know how an issue as substantial as this was not addressed prior to the new
dependency management library and related changes being released.
To make our projects work in Eclipse, developers run maven outside of Eclipse
to resolve the ranges, go back into Eclipse and refresh dependencies. And when
they want to get latest/greatest, they have to get a fresh pom.xml and repeat.
Royal PITA. And because the m2e project insists that an embedded Maven3 is
required for resolving dependencies, there's no workaround other than rewriting
the plugin myself (not trivial, do not have the time), and in the meantime I'm
dealing with upset developers
Without the issue being resolved soon, I don't believe I'm the only one who
will need to consider options outside of Maven.
> Version ranges with non-snapshot bounds can contain snapshot versions
> ---------------------------------------------------------------------
>
> Key: MNG-3092
> URL: https://jira.codehaus.org/browse/MNG-3092
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Reporter: Mark Hobson
> Assignee: Jason van Zyl
> Fix For: 3.1.1
>
> Attachments: MNG-3092.patch, 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
