[
http://jira.codehaus.org/browse/MNG-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231034#action_231034
]
Benjamin Bentmann commented on MNG-4751:
----------------------------------------
This was an intentional change to fix MNG-3092. The new behavior is apparently
as controversial as the previous one, so feel free to join the related
discussion [Resolving SNAPSHOTs from Version Ranges in Maven
3|http://maven.40175.n5.nabble.com/Resolving-SNAPSHOTs-from-Version-Ranges-in-Maven-3-td2257936.html]
> Snapshot version not resolved for version range
> -----------------------------------------------
>
> Key: MNG-4751
> URL: http://jira.codehaus.org/browse/MNG-4751
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.0-beta-1
> Environment: linux x86_64, sun java 1.6.0_14
> Reporter: Brian Kramer
> Priority: Blocker
> Attachments: snapshot_dep.zip
>
>
> Even with a snapshot dependency in the pom, a release version is included in
> the classpath for compilation.
> This happens when a mid-level dependency and the top-level project both
> depend on the same artifact. The mid-level dependency selects a range of
> valid versions which includes the snapshot version and the top-level project
> depends explicitly on the snapshot version.
> This is a regression from 2.2.1
> To reproduce:
> 1. Release/deploy/install v1.0 of tlib
> 2. deploy v1.1-SNAPSHOT of tlib
> 3. Release/deploy/install v1.0 of tlib2
> 4. Try to compile tapp
--
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
