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 versions but not the 2.0 GA release so there is no reason you need [1.0,2.0) to do the exact same thing... :-)
Mark D's workaround is a pragmatic approach. As for why I don’t get involved, I tend to be selective about where I spend my time and since we eliminated the use of version ranges in our projects for multiple reasons, addressing this issue doesn't really meet my bar for investing my time to contribute. I do contribute periodically, still waiting on my latest bug fix to be integrated (https://issues.apache.org/jira/browse/MNG-5889)... Cheers, Robert -----Original Message----- From: Curtis Rueden [mailto:[email protected]] Sent: Friday, September 23, 2016 3:45 PM To: Maven Users List Cc: [email protected] 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 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 <[email protected]> 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:[email protected]] > 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: [email protected] > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
