We use 4 digit build numbers and I never noticed it. Probably because we control our versions very carefully and maven doesn't have to figure it out for us. This could be an issue though.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Tuesday, December 12, 2006 5:48 AM To: Maven Developers List Subject: Re: maven2 repository of eclipse jars On 12/11/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote: > - the 4th token MUST be separated with "-" in maven, while in osgi > MUST be "." (this is handled by the make-artifacts goal actually). A > version like 1.2.3-4 in maven is parsed as [major 1, minor 2, patch 3, > build 4], a version like 1.2.3.4 is parsed as [major 0, minor 0, patch > 0, build 0, qualifier "1.2.3.4"] (funny, I discovered this only > recently by looking at DefaultVersion unit tests... I can't say I like > it but that's how maven works and it's expected to work, you will > never notice it till you will experiment 4 digits version numbers, and > osgi bundles HAVE 4 digits version numbers). i'd say that's a bug more than a "feature", I given the increasing importance OSGi is getting we should probably accommodate it. For what you say we need the build number as part of the version in eclipse stuff. There's no such thing as 3.2.0, it'll be always 3.2.0.x and that should be the Maven version -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --------------------------------------------------------------------- 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]
