Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
MIME-Version: 1.0
Sender: ctrueden.wisc@gmail.com
In-Reply-To: <d27ccf62-f2b0-4948-acf6-67bf5242e2c9@default>
References: <F21547B4F425F9428444D12A512705066D27221E@NP1EXMB105.corp.halliburton.com>
 <CADN69ynC1LwiNAassQa1Zf3zY+DvvmvgGd6vE5Rz4xRkAo2hHQ@mail.gmail.com>
 <F21547B4F425F9428444D12A512705066D27234D@NP1EXMB105.corp.halliburton.com>
 <c8bd63f3-234b-40a6-b3a7-34524d4d5fb3@default> <20160923163141.59F7229C03F5@dd17332.kasserver.com>
 <6062cdce-945e-4ec6-a038-b1f8dd786348@default> <57f108d5-b7ca-8391-1c53-0eac274970e9@gmx.de>
 <d27ccf62-f2b0-4948-acf6-67bf5242e2c9@default>
From: Curtis Rueden <ctrueden@wisc.edu>
Date: Fri, 23 Sep 2016 15:44:51 -0500
Message-ID: <CADN69ynHdW3DuefJTLx_Yo13vFGhjmURhQ7Ebs61Kv9eoqOmng@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: help with version range
To: Maven Users List <users@maven.apache.org>
Cc: info@soebes.de
Content-Type: multipart/alternative; boundary=001a114b74dc632851053d32dbbf
archived-at: Fri, 23 Sep 2016 20:45:27 -0000

--001a114b74dc632851053d32dbbf
Content-Type: text/plain; charset=UTF-8

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 unsubstantiated to claim "most people" here.

> There should be a simple way to achieve this

I agree. Why not propose a new syntax, or even a patch? Maven is open
source.

Regards,
Curtis


--
Curtis Rueden
LOCI software architect - http://loci.wisc.edu/software
ImageJ2 lead, Fiji maintainer - http://imagej.net/User:Rueden
Did you know ImageJ has a forum? http://forum.imagej.net/


On Fri, Sep 23, 2016 at 3:41 PM, Robert Patrick <robert.patrick@oracle.com>
wrote:

> 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 fight Maven to achieve this is a pain--and I have
> been using Maven for many years now.  There should be a simple way to
> achieve this that does not require me to do something like this:
>
> [1.0,1.999999999999999999999999999999999999999999999999999999999999
> 999999999999999999999999999)
>
>
> -----Original Message-----
> From: Karl Heinz Marbaise [mailto:khmarbaise@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" 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 is the timeline of those releases...
> So a pre-release (2.0-alpha-1, 2.0-RC1 etc.) will be done before the final
> release (2.0) so must be defined as before...
>
> Kind regards
> Karl Heinz Marbaise
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

--001a114b74dc632851053d32dbbf--