Dependency range resolution resolves to SNAPSHOTS!?

Hi all, We recently (during the last weeks) ran into a situation where version ranges (e.g. [1.0,) ) where resolved to SNAPSHOT versions as well. My understanding was always that if I specify a non-snapshot version in a range that only released version will be resolved. Is my understanding

Re: Dependency range resolution resolves to SNAPSHOTS!?

2008/10/8 Stefan Fritz [EMAIL PROTECTED]: Hi all, We recently (during the last weeks) ran into a situation where version ranges (e.g. [1.0,) ) where resolved to SNAPSHOT versions as well. My understanding was always that if I specify a non-snapshot version in a range that only released

Re: Dependency range resolution resolves to SNAPSHOTS!?

On Thu, 09 Oct 2008 01:20:42 Mark Hobson wrote: 2008/10/8 Stefan Fritz [EMAIL PROTECTED]: Hi all, We recently (during the last weeks) ran into a situation where version ranges (e.g. [1.0,) ) where resolved to SNAPSHOT versions as well. My understanding was always that if I specify a

RE: Weird behaviour with dependency range

Looks like the same npe as MNG-3372 and MNG-3351 -Original Message- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Monday, February 11, 2008 7:51 AM To: users@maven.apache.org Subject: Weird behaviour with dependency range Hi, I've run across something very odd with dependency

Weird behaviour with dependency range

Hi, I've run across something very odd with dependency ranges. Maven version: 2.0.8 java: 1.6 If I put this in my pom dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version[1.0.9]/version /dependency then run dependency:tree I get an

RE: Weird behaviour with dependency range

behaviour with dependency range Hi, I've run across something very odd with dependency ranges. Maven version: 2.0.8 java: 1.6 If I put this in my pom dependency groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId version[1.0.9]/version

Dependency range and SNAPSHOT

I'm trying to understand how version range work. I have a parent pom that define version in its dependencyManagement section. For one of my project, it defines it as : [0.1.2,) When doing a mvn dependency:resolve, I see that it is resolved to 0.1.3-SNAPSHOT. I agree that 0.1.3-SNAPSHOT is newer

RE: Dependency range and SNAPSHOT

. Regards, Dave -Original Message- From: Guillaume Lederrey [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 10:14 AM To: Maven Users List Subject: Dependency range and SNAPSHOT I'm trying to understand how version range work. I have a parent pom that define version in its

Re: Dependency range and SNAPSHOT

, MRELEASE-262, possibly more... There is work going on to resolve these, please check the jira's and help if you can. Regards, Dave -Original Message- From: Guillaume Lederrey [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 23, 2008 10:14 AM To: Maven Users List Subject: Dependency

Dependency range check for a.b.c.d

Hi, I couldn't find that question here yet, so I am gonna ask it. Is it possible that Maven2 has a problem with version range checks like version[1.9.4.11, )/version In the Debug output I get this: [DEBUG] jide:jide-common:jar:1.9.3:compile (setting version to: 1.9.3 from range:

Re: Dependency range check for a.b.c.d

Version ranges are known to be somewhat broken in Maven 2.0 right now. Here's a bug I filed: http://jira.codehaus.org/browse/MNG-2210 Wayne On 3/29/07, Mirko Leschikar [EMAIL PROTECTED] wrote: Hi, I couldn't find that question here yet, so I am gonna ask it. Is it possible that Maven2 has a

Dependency range

When I have a range for a dependency in an artifact and I deploy that artifact, will it keep the dependency range in the pom's artifact that gets deployed with it? Or will it set the version used to create the artifact? Is it possible to know what version of each dependency used during