On 18/09/2009, at 6:00 PM, Stephen Connolly wrote:
To avoid the last issue, I would use versions like this:
1.4.2_05
1.4.2_19
They will continue sorting correctly for version ranges as long as
we never
get into 1.4.12 which given the history of Java versioning is pretty
unlikely.
Then you have the build number in case you make a mistake (though I'd
recommend being extra careful about making sure they are correct
before
releasing anything).
actually if we go with the above we no longer have the build number as
the entire version is now a qualifier and version ranges have become
rather troublesome
I'm not sure working around bugs in Maven and trying to predict the
future is going to be too fruitful.
Do you have concrete use cases for version ranges? If so, do you need
Maven to resolve them or will you be resolving them yourself? (in
which case you can make corrections)
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
