Re: [EXTERNAL] Re: help with version range

; > semantics. > > > > > > -Original Message- > > From: Manfred Moser [mailto:manf...@simpligility.com] > > Sent: Friday, September 23, 2016 11:32 AM > > To: users@maven.apache.org > > Subject: Re: [EXTERNAL] Re: help with version range >

Re: [EXTERNAL] Re: help with version range

; 99) > > > -Original Message- > From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] > Sent: Friday, September 23, 2016 3:30 PM > To: Maven Users List > Subject: Re: [EXTERNAL] Re: help with version range > > Hi, > > On 23/09/16 18:38,

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

...@schulte.it] Sent: Friday, September 23, 2016 8:47 PM To: Maven Users List <users@maven.apache.org> Subject: 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 exc

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

om: Robert Patrick [mailto:robert.patr...@oracle.com] Sent: Friday, September 23, 2016 4:39 PM To: Maven Users List <users@maven.apache.org> Subject: RE: [EXTERNAL] Re: help with version range This is nice, but it doesn’t work in Maven

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

version], C:\myproject\zipinsall\pom.xml, line 196, column 22 -Original Message- From: Christian Schulte [mailto:c...@schulte.it] Sent: Friday, September 23, 2016 5:17 PM To: Maven Users List Subject: Re: [EXTERNAL] Re: help with version range Am 09/23/16 um 23:38 schrieb Rob

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

chulte.it] Sent: Friday, September 23, 2016 4:23 PM To: Maven Users List Cc: i...@soebes.de Subject: 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://ma

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

- From: Curtis Rueden [mailto:ctrue...@wisc.edu] Sent: Friday, September 23, 2016 3:45 PM To: Maven Users List Cc: i...@soebes.de Subject: Re: [EXTERNAL] Re: help with version range Hi Robert, > most people that use version ranges that use a non-inclusive top-end > specification do no

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

khmarba...@gmx.de] > Sent: Friday, September 23, 2016 3:30 PM > To: Maven Users List > Subject: 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"

RE: [EXTERNAL] Re: help with version range

Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Friday, September 23, 2016 3:30 PM To: Maven Users List Subject: 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"

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: [EXTERNAL] Re: help with version range

(2|2.0|2.0.0)-(a|alpha)-SNAPSHOT Verzonden vanaf Samsung Mobile. Oorspronkelijk bericht Van: Robert Patrick <robert.patr...@oracle.com> Datum:23-09-2016 11:18 (GMT-08:00) Aan: Maven Users List <users@maven.apache.org> Onderwerp: RE: [EXTERNAL] Re: help with v

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

ailto:manf...@simpligility.com] Sent: Friday, September 23, 2016 11:47 AM To: users@maven.apache.org Subject: 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

RE: [EXTERNAL] Re: help with version range

fred Moser [mailto:manf...@simpligility.com] Sent: Friday, September 23, 2016 11:47 AM To: users@maven.apache.org Subject: 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 wit

Re: [EXTERNAL] Re: help with version range

iday, September 23, 2016 11:32 AM > To: users@maven.apache.org > Subject: 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 > o

Re: [EXTERNAL] Re: help with version range

gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf > Of Curtis Rueden > Sent: Friday, September 23, 2016 9:01 AM > To: Maven Users List > Subject: [EXTERNAL] Re: help with version range > > Hi Justin, > > You could write "[1.1.0,1.1.9]", no? A bit hacky, but would

RE: [EXTERNAL] Re: help with version range

t; nothing related to 2.0... > > -Original Message- > From: Justin Georgeson [mailto:jgeorge...@lgc.com] > Sent: Friday, September 23, 2016 10:11 AM > To: Maven Users List > Subject: RE: [EXTERNAL] Re: help with version range > > Yeah, I was hoping there was something

Re: [EXTERNAL] Re: help with version range

t; > -Original Message- > From: Justin Georgeson [mailto:jgeorge...@lgc.com] > Sent: Friday, September 23, 2016 10:11 AM > To: Maven Users List > Subject: RE: [EXTERNAL] Re: help with version range > > Yeah, I was hoping there was something more elegant like 1.1

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 ver

RE: [EXTERNAL] Re: help with version range

, what I mean when I say [1.0,2.0) is any 1.x version but nothing related to 2.0... -Original Message- From: Justin Georgeson [mailto:jgeorge...@lgc.com] Sent: Friday, September 23, 2016 10:11 AM To: Maven Users List Subject: RE: [EXTERNAL] Re: help with version range Yeah, I was hoping

RE: [EXTERNAL] Re: help with version range

the pre-release versions? -Original Message- From: ctrueden.w...@gmail.com [mailto:ctrueden.w...@gmail.com] On Behalf Of Curtis Rueden Sent: Friday, September 23, 2016 9:01 AM To: Maven Users List Subject: [EXTERNAL] Re: help with version range Hi Justin, You could write "[1.1.0,1.1.

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