Carlos Sanchez wrote:
the repository has some rules and you have to follow them to be
manageable, eg. you name jars artifactId-version.jar and not
otherwise. If there are version rules you'd have to follow, and I
don't see the problem in having a standardized version convention, as
we have standardized folder names.
As I said before:
The problem is basically that this simply isn't powerful enough to
cover all the various versioning schemes there are in the wild.
Suggesting forcing everybody to conform to your idea of versioning
isn't at all helpful; similarly imposing a complex mapping between
upstream and maven versions for a project is unattractive.
Which part do you disagree with?
--
Richard van der Hoff <[EMAIL PROTECTED]>
Telephony Gateways Project Manager
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
