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.999999999999999999999999999999999999999999999999999999999999999999999999999999999999999) -----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, 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-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
