Re: [EXTERNAL] Re: help with version range

Am 09/24/16 um 04:16 schrieb Justin Georgeson: > I tried these four version ranges with the 3.4.0-SNAPSHOT from your link > > [1.1.min,1.1.max] > [1.1.*] > [1.2.min,1.2.max] > [1.2.*] > > All four downloaded the expected parent POM without the warnings. That's expected behaviour. Damn it ;-)

RE: [EXTERNAL] Re: help with version range

I tried these four version ranges with the 3.4.0-SNAPSHOT from your link [1.1.min,1.1.max] [1.1.*] [1.2.min,1.2.max] [1.2.*] All four downloaded the expected parent POM without the warnings. I like the colorized output. -Original Message- From: Christian Schulte

Re: [EXTERNAL] Re: help with version range

Am 09/24/16 um 02:15 schrieb Justin Georgeson: > The Aether doc shows both bounds being inclusive with the min/max form, but > you have an exclusive upper bound. Using "[1.1.min,1.1.max]" is working for > me with both 3.2.5 and 3.3.9. So that's awesome! The .* form is working for > me too. I'm

RE: [EXTERNAL] Re: help with version range

The Aether doc shows both bounds being inclusive with the min/max form, but you have an exclusive upper bound. Using "[1.1.min,1.1.max]" is working for me with both 3.2.5 and 3.3.9. So that's awesome! The .* form is working for me too. I'm using JDK 1.8.0_102, and my projects are pretty much

Re: [EXTERNAL] Re: help with version range

Am 09/24/16 um 00:23 schrieb Robert Patrick: > That one is even worse, pom parsing fails... > > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > [ERROR] 'dependencies.dependency.version' for myproject:util:jar must not > contain any of these characters \/:"<>|?* but

RE: [EXTERNAL] Re: help with version range

That one is even worse, pom parsing fails... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [ERROR] 'dependencies.dependency.version' for myproject:util:jar must not contain any of these characters \/:"<>|?* but found * @ myproject:zip-installer:[unknown-version],

Re: [EXTERNAL] Re: help with version range

Am 09/23/16 um 23:38 schrieb Robert Patrick: > This is nice, but it doesn’t work in Maven 3.3.9... > > [ERROR] org.apache.maven.project.artifact.InvalidDependencyVersionException: > Invalid version: [0.8.min,0.8.max] found for: Dependency: myproject:util in > project:

RE: [EXTERNAL] Re: help with version range

This is nice, but it doesn’t work in Maven 3.3.9... [ERROR] org.apache.maven.project.artifact.InvalidDependencyVersionException: Invalid version: [0.8.min,0.8.max] found for: Dependency: myproject:util in project: myproject:zip-installer:pom:0.9-SNAPSHOT. Reason: Range defies version ordering:

Re: Excluding transitive dependencies of plugins

Any pointers please? Thanks Gaurav On Mon, Sep 19, 2016 at 5:51 PM, Gaurav Gupta wrote: > Hi, > > I have a use case where I need to exclude transitive dependency of a > plugin. > I am using following plugin > > org.codehaus.mojo > cobertura-maven-plugin > 2.7 > > This

Re: [EXTERNAL] Re: help with version range

Am 09/23/16 um 23:07 schrieb Robert Patrick: > There is already a syntax to give you pre-release versions, right? According > to > https://maven.apache.org/ref/3.3.9/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html, > the range [1.0,2.0-SNAPSHOT] will give you

RE: [EXTERNAL] Re: help with version range

There is already a syntax to give you pre-release versions, right? According to https://maven.apache.org/ref/3.3.9/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html, the range [1.0,2.0-SNAPSHOT] will give you the newest release including all 2.0 prerelease

Re: help with version range

On 24 Sep 2016, at 1:38, Justin Georgeson wrote: > ’m using the parent version range feature with “[1.1.0,1.2.0)” and it had > been going well. However I wanted to start working on 1.2.0 of the parent, so > I published a 1.2.0-alpha-1 version. And all the projects with te > “[1.1.0,1.2.0)”

Re: [EXTERNAL] Re: help with version range

Hi Robert, > most people that use version ranges that use a non-inclusive top-end > specification do not want prerelease versions included. I have yet to > hear you or anyone else give me a use case where you want this. Personally, I want prerelease versions included. I think it is

RE: [EXTERNAL] Re: help with version range

Well...like I said, I understand the relationship but clearly, most people that use version ranges that use a non-inclusive top-end specification do not want prerelease versions included. I have yet to hear you or anyone else give me a use case where you want this. The fact that I have to

Re: [EXTERNAL] Re: help with version range

Hi, BTW the behaviour of Maven's version comparision can be simply shown by using the following: java -jar /usr/local/apache-maven-3.3.9/lib/maven-artifact-3.3.9.jar 2.0-alpha-1 2.0-SNAPSHOT Display parameters as parsed by Maven (in canonical form) and comparison result: 1. 2.0-alpha-1 ==

Re: [EXTERNAL] Re: help with version range

Hi, On 23/09/16 18:38, Robert Patrick wrote: What I am questioning is the "engineer's approach" to version range resolution without > a valid use case for why Maven should consider > pre-released versions as within the "not including 2.0" version > range semantics. The simple answer to this

Re: SNAPHOST Depedency of plugin not found

Hi Oliver, please show your pom as Chris already mentioned... Kind regards Karl Heinz Marbaise On 23/09/16 10:54, Oliver B. Fischer wrote: Hi, I have a plugin dependency (currently only available as SNAPSHOT) declared for the Maven dependency plugin. If I declare it only as dependency of the

RE: [EXTERNAL] Re: help with version range

(2|2.0|2.0.0)-(a|alpha)-SNAPSHOT Verzonden vanaf Samsung Mobile. Oorspronkelijk bericht Van: Robert Patrick Datum:23-09-2016 11:18 (GMT-08:00) Aan: Maven Users List Onderwerp: RE: [EXTERNAL] Re: help with version range

RE: [EXTERNAL] Re: help with version range

So then the right range to keep all 2.0 pre-release artifacts out of the build is [1.0,2.0-a)? -Original Message- From: Guillaume Boué [mailto:gb...@apache.org] Sent: Friday, September 23, 2016 12:12 PM To: users@maven.apache.org Subject: Re: [EXTERNAL] Re: help with version range

Re: [EXTERNAL] Re: help with version range

Maven will consider 2.0-alpha-1 to be before 2.0-SNAPSHOT. This is documented in ComparableVersion: https://maven.apache.org/ref/3.3.9/maven-artifact/apidocs/org/apache/maven/artifact/versioning/ComparableVersion.html. Guillaume Le 23/09/2016 à 18:49, Robert Patrick a écrit : I was not

RE: [EXTERNAL] Re: help with version range

I was not suggesting that it could be changed...only that it doesn't make sense (except from a pure mathematical point of view). Given this "engineer's approach" to version range resolution, it seems like a better idea is simply to say [1.0,2.0-SNAPSHOT). I have verified that this eliminates

Re: [EXTERNAL] Re: help with version range

Fair enough. From the purely engineering/mathematical point of view it might not make sense. But I dont see a way to get that changed with breaking a TON of other stuff. And I am not even sure if it would be more intuitive instead of just being different. Manfred Robert Patrick wrote on

Re: [EXTERNAL] Re: help with version range

Hi Justin, > Logically, does it make sense to resolve 1.2.0-alpha-1 when the user > has excluded 1.2.0 from their range? If I explicitly don't want the > release version why would I want the pre-release versions? I think it really depends how you use those version suffixes. For example, I have a

RE: [EXTERNAL] Re: help with version range

No, you are making an invalid assumption about what I understand! I completely understand the relationship of SNAPSHOTs and other pre-release artifacts and released versions. What I am questioning is the "engineer's approach" to version range resolution without a valid use case for why

Re: [EXTERNAL] Re: help with version range

What you are misunderstanding is how snapshots are meant to be used. 2.0-SNAPSHOT means that it is a development version working towards the release of 2.0 and as such the version 2.0-SNAPSHOT is smaller than 2.0. If you mislike this you can change how you work with your own projects at least.

RE: [EXTERNAL] Re: help with version range

Similarly I wouldn't want a range like "[1.2.0,1.3.0)" to give me a pre-release 1.2.0 artifact. -Original Message- From: Robert Patrick [mailto:robert.patr...@oracle.com] Sent: Friday, September 23, 2016 10:56 AM To: Maven Users List Subject: RE: [EXTERNAL] Re: help with version range

RE: [EXTERNAL] Re: help with version range

This does seem non-intuitive.If I say that I want versions between 1.0 and up to but NOT including 2.0 by saying [1.0,2.0), in what use case would I ever want this to resolve to 2.0-SNAPSHOT or any other pre-release 2.0 artifact? Personally, I cannot think of a single one. Typically,

RE: [EXTERNAL] Re: help with version range

Yeah, I was hoping there was something more elegant like 1.1+ or something, so I can at least move forward with that. Logically, does it make sense to resolve 1.2.0-alpha-1 when the user has excluded 1.2.0 from their range? If I explicitly don't want the release version why would I want the

Re: SNAPHOST Depedency of plugin not found

Hi Oliver, Can you share your POM? Did you configure the ? Regards, Curtis On Sep 23, 2016 3:54 AM, "Oliver B. Fischer" wrote: > Hi, > > I have a plugin dependency (currently only available as SNAPSHOT) declared > for the Maven dependency plugin. > > If I declare it

Re: help with version range

Hi Justin, You could write "[1.1.0,1.1.9]", no? A bit hacky, but would match the versions you want in practice. Regards, Curtis On Sep 23, 2016 8:38 AM, "Justin Georgeson" wrote: > I’m using the parent version range feature with “[1.1.0,1.2.0)” and it had > been going

help with version range

I'm using the parent version range feature with "[1.1.0,1.2.0)" and it had been going well. However I wanted to start working on 1.2.0 of the parent, so I published a 1.2.0-alpha-1 version. And all the projects with te "[1.1.0,1.2.0)" picked it up. I recognize that this is in keeping with the

SNAPHOST Depedency of plugin not found

Hi, I have a plugin dependency (currently only available as SNAPSHOT) declared for the Maven dependency plugin. If I declare it only as dependency of the plugin Maven is tries to find it at http://repository.apache.org/snapshots. If I declare it also as normal dependency of the project