maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Derricutt (JIRA)" <>
Subject [jira] Commented: (MNG-4751) Snapshot version not resolved for version range
Date Thu, 05 Aug 2010 20:12:32 GMT


Mark Derricutt commented on MNG-4751:

This now seems to be affecting IntelliJ IDEA as well ( at least I suspect this might be the
reason ), as the IDE's maven support now resolves all project artifacts to the released version,
rather than the -SNAPSHOT version in the opened project, which means you get the annoying
behavior of single stepping into, and breakpoints stopping on .class entries from a jar file
rather than the .java file in our source paths.

As mentioned in MNG-3092 - I love this feature -FOR RELEASES- where I wholeheartedly only
want to resolve released artifacts so that any API breakages are caught that otherwise might
leak in without a proper version bump ( 1.2.4 -> 1.3.1 for instance ) - but for integration
tests, distribution builds, and IDE integration I think having the old behavior is preferred.

Off by default would be fine by me, as long as I can enable it for projects that explicitly
say "give me the bleeding edge", possibly via a POM element ( schema breaking tho ), a plugin
configuration, or just a system property that one needs to set.

I was pointed at yesterday (IntelliJ bug report)
for some maven resolution oddities which I commented on about this range issue, however they
may or may not be related.

> Snapshot version not resolved for version range
> -----------------------------------------------
>                 Key: MNG-4751
>                 URL:
>             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:
> 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:
For more information on JIRA, see:


View raw message