[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323035#comment-323035 ]
Scott Sosna commented on MNG-3092: ---------------------------------- We use Artifactory, I've looked before and saw nothing in the logs but I'll review again. Regardless, the time spent resolving via Maven2 is substantially less than through Maven3, and what I notice is that on a version range it seems to continually pull down/review all metadata rather than the latest version. For the m2e Eclipse plugin, it can cause simple projects (A depends on B depends on C) to take 45+ minutes to update. The project dependency graph is fairly simple, no circular loops, just a simple tree (at most 4 levels deep, but mostly 2 or 3). At minimum we have 1 new snapshot per day, but often more than that, each with its own build number. I've tried deleting decently-old snapshots, but hasn't helped performance much. This shouldn't be considered too complex by any stretch of the imagination. > 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