[jira] Commented: (MNG-4751) Snapshot version not resolved

["Brian Kramer (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MNG-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=231031#action_231031 ] 

Brian Kramer commented on MNG-4751:
-----------------------------------

I found a workaround, I'm not sure that this is the intended behavior but if you make the snapshot a single inclusive range then it works.

in tapp/pom.xml:
    <dependency>
      <groupId>org.tlib</groupId>
      <artifactId>tlib</artifactId>
      <version>[1.1-SNAPSHOT]</version>
    </dependency>


> Snapshot version not resolved
> -----------------------------
>
>                 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