[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=362616#comment-362616 ]
Jon Harper commented on MNG-3092: --------------------------------- Hi, I'm new to this discussion. A first objective is to get the documentation to match the implementation. The link (http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution) in the original description of this issue seems to be the only documentation of version ranges. But it is *not* documentation, it's a design document. People are turning to it because the real documentation is missing. I think that if we fix the real documentation, it will prevent more confusion. So I think we need to add documentation to "http://maven.apache.org/pom.html". Right now, it has a section on dependencies stating: {quote} groupId, artifactId, version: These elements are self-explanatory {quote} *I think this is the root of all the _pain_ and _frustration_ in this thread*. It's incredibly frustrating and upsetting that this huge issue was being dismissed as "self-explanatory" in the docs the whole time. I would be willing to spend time to work and collaborate on improving the documentation. Does anyone know who can be contacted to change http://maven.apache.org/pom.html ? > resolution of version ranges with non-snapshot bounds can resolve to a > snapshot version > --------------------------------------------------------------------------------------- > > Key: MNG-3092 > URL: https://jira.codehaus.org/browse/MNG-3092 > Project: Maven > Issue Type: Bug > Components: Dependencies > Reporter: Mark Hobson > Assignee: Jason van Zyl > Fix For: 3.2.x > > 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 was sent by Atlassian JIRA (v6.1.6#6162)