On Tue, 13 Jun 2006, Sakala, Adinarayana wrote: Hi,
Yes. I've just tested this with some new unit testsnew unit tests in maven-artifact's DefaultArtifactVersion. The testcase reports that "2.0.1-xyz" < "2.0.1" < "2.0.1-123". -- Kenney > Hi, > > We are having a discussion on how to version Yoko's first milestone release. > Can somebody clarify and confirm on how maven deals with version tag. > The question is, will "1.0" version tag be considered as greater/latest > compared to "1.0-incubating-M1"? > i.e > x.y.z-alphabetic < x.y.z < x.y.z-numeric > > FYI, Yoko uses Maven 2.0.4 > > thanks, > Adi Sakala > > > -----Original Message----- > > From: David Jencks [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 12, 2006 9:11 PM > > To: [email protected] > > Subject: Re: Yoko version... (WAS: RE: Steps for hitting a Milestone > > release (WAS: RE: Milestone release)) > > > > > > > > On Jun 12, 2006, at 5:48 PM, Daniel Kulp wrote: > > > > > > > > David, > > > > > >> I assume this is maven2 we're talking about... > > >> > > >> My understanding is that > > >> > > >> x.y.z-alphabetic > > >> precedes > > >> x.y.z > > >> which precedes > > >> x.y.z-numeric > > > > > > Is this documented someplace? > > > > > > I'm not sure I'm entirely accurate here, however I'm sure that x.y.z- > > incubating is before x.y.z > > > > This is discussed in "Better builds with maven" page 59. > > > > thanks > > david jencks > > > > > > > I went thought most of the "mini guides" on > > > the maven website and didn't see anything which is why I > > raised the > > > concern. > > > I'd rather not rely on undocumented behavior that just happens to > > > do what we > > > want. Then again, much of maven's behavior falls into that > > > category. :-( > > > (honestly, I LIKE maven, but sometimes, all you can do is just > > > shake your > > > head and wonder.....) > > > > > > > > >> Thus 1.0-SNAPSHOT is before 1.0, and build 1 (1.0-1) is after 1.0. > > > > > > SNAPSHOT's are special cases as you need to explicitly enable > > > them. My > > > understanding is the -SNAPHOST tail is treated completely special > > > so that > > > they can be completely turned off, the release plugin can "flag" > > > them, etc... > > > > > > > > >>>> My suggestion is to just play it safe and make sure the first > > >>>> "#.#" is there > > >>>> and is incremented in some fassion for each release. > > >>> > > >>> So, its sounds like going with your suggestion is a better idea. > > >>> i.e 0.1-incubating-M1 > > >>> > > >>> Any objections to this change? > > >> > > >> If this contains pretty much the intended feature set for > > 1.0, I'd go > > >> with 1.0-incubating-M1. If there's enormous missing functionality, > > >> 0.1-incubating-M1 seems more appropriate. I was under the > > impression > > >> that the former was more accurate :-) > > > > > > Ok, how about 0.9-incubating-M1? :-) > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
