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 2016-09-23 09:38: > 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 Maven should consider pre-released versions > as > within the "not including 2.0" version range semantics. > > > -----Original Message----- > From: Manfred Moser [mailto:[email protected]] > Sent: Friday, September 23, 2016 11:32 AM > To: [email protected] > 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 > 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. .. you can just call your snapshot version 1.99-SNAPSHOT or whatever > while developing and at releas time switch to 2.0 .. > > Manfred > > Robert Patrick wrote on 2016-09-23 08:56: > >> 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, 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:[email protected]] >> 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+ 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 pre-release versions? >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] 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.99999]", no? A bit hacky, but would match >> the versions you want in practice. >> >> Regards, >> Curtis >> >> On Sep 23, 2016 8:38 AM, "Justin Georgeson" <[email protected]> wrote: >> >>> 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 implementation that x.y.z-(alpha|beta|…) >>> precedes x.y.z, but it is unintuitive to me. First in that I’ve >>> stated I don’t want 1.2.0, and second that once I do release 1.2.0 >>> the projects which were receiving the alpha builds will not get >>> 1.2.0. I tried with both >>> 3.2.5 and 3.3.9. Can the version range syntax express the range I want? >>> >>> >>> >>> *Justin Georgeson* >>> Landmark Cloud Platforms & DevOps - RM >>> >>> Email: *[email protected]* <[email protected]> >>> >>> Follow Halliburton: *LinkedIn* >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dho >>> s >>> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatur >>> e >>> s-255d-26url-3Dhttp-3A__www.linkedin.com_company_halliburton&d=DQIFaQ >>> & >>> c=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo&r=dLxYM3PBhAqFnkH7uKz_O >>> V >>> ZL1uyui4QoEmBCjCmEiTk&m=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8&s >>> = 9g208ksOttPVrCNlOx459-qzk0wWAei89_zhZnej5vM&e= > >>> | *Facebook* >>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__logw332.ati-2Dh >>> o >>> st.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatu >>> r >>> es-255d-26url-3Dhttps-3A__www.facebook.com_halliburton&d=DQIFaQ&c=Psk >>> v >>> ixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo&r=dLxYM3PBhAqFnkH7uKz_OVZL1uy >>> u >>> i4QoEmBCjCmEiTk&m=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8&s=NgT-w >>> O jrb7gpKDJVcRDMmKUQqGfR-PSnXe3I98Lp1c4&e= > >>> | *Twitter* >>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__logw332.ati-2Dh >>> o >>> st.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatu >>> r >>> es-255d-26url-3Dhttps-3A__twitter.com_halliburton&d=DQIFaQ&c=PskvixtE >>> U >>> DK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo&r=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4Qo >>> E >>> mBCjCmEiTk&m=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8&s=-swEvm-8NW >>> 2 18tPAkOpg46kdPblTNts2y7dbe_w82wM&e= > >>> | *YouTube* >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dho >>> s >>> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatur >>> e >>> s-255d-26url-3Dhttp-3A__youtube.com_halliburton&d=DQIFaQ&c=PskvixtEUD >>> K >>> 7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo&r=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEm >>> B >>> CjCmEiTk&m=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8&s=dTvvV1RKdjYS >>> K >>> _Hc5JX55QI7b2j-A4O9RAX2Dg9qbrU&e= > >>> | *Blog* >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__logw332.ati-2Dho >>> s >>> t.net_gopc.url-3Fxts-3D553058-26xtor-3DEPR-2D25-2D-255bHAL-2Dsignatur >>> e >>> s-255d-26url-3Dhttp-3A__halliburtonblog.com&d=DQIFaQ&c=PskvixtEUDK7wu >>> W >>> U-tIg6oKuGYBRbrMXk2FZvF0UfTo&r=dLxYM3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjC >>> m >>> EiTk&m=y4-iycjs7jCDUAa82A-SQP4DqefDDZjCpFKXFWCrmu8&s=Or-LJ9tIt99DaFT0 >>> - >>> BpnvVYmC73xtz0gLUBwIg5Woho&e= > >>> >>> >>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.landmark.so >>> l >>> utions_&d=DQIFaQ&c=PskvixtEUDK7wuWU-tIg6oKuGYBRbrMXk2FZvF0UfTo&r=dLxY >>> M >>> 3PBhAqFnkH7uKz_OVZL1uyui4QoEmBCjCmEiTk&m=y4-iycjs7jCDUAa82A-SQP4DqefD >>> D ZjCpFKXFWCrmu8&s=f4P54iKSAZYutrqVX1iHAWO9C7nP1vrd3OJGBT9g4LE&e= > >>> >>> >>> >>> >>> ------------------------------ >>> This e-mail, including any attached files, may contain confidential >>> and privileged information for the sole use of the intended recipient. >>> Any review, use, distribution, or disclosure by others is strictly >>> prohibited. >>> If you are not the intended recipient (or authorized to receive >>> information for the intended recipient), please contact the sender by >>> reply e-mail and delete all copies of this message. >>> >> >> --------------------------------------------------------------------- >> 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] > > > --------------------------------------------------------------------- > 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]
