Since it doesn't change the parsing of the standard maven version string, I think the risk is pretty low. I see it as basically better handling of one type of non-standard format. But I understand your concern, that's why I brought it up for discussion ;)

Brian E. Fox wrote:
These kinds of changes in the 2.0.x branch concern me. There's no way to
predict what impact this will have out there.

-----Original Message-----
From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Thursday, April 17, 2008 5:23 AM
To: Maven Developers List
Subject: Re: Change to artifact version handling.

I haven't yet applied it, but at first thought it seems a reasonable change.

- Brett

On 16/04/2008, at 6:37 AM, Paul Gier wrote:

Hi everyone,

I'd like to make a small change to the artifact version parsing. We currently have several released projects that use a non-standard version scheme. So instead of something like:
1.0.1-beta-1
we have
1.0.1.beta1

This was originally done to conform to the OSGi standard which requires a "." instead of a "-" for the qualifier. If you ask me, the maven standard is better ;)

I created a jira issue with the attached fix here:
http://jira.codehaus.org/browse/MNG-3526

Since this change could potentially (although I think unlikely) break some dependency management I wanted to bring it up here to discuss.

Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
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]

Reply via email to