hello, option 1 will be a good solution with the drawback that some people will fall into trouble because they are "not allowed" to change anything and cannot upgrade (belong to theses...)
option 3 is the best world to me I think that a naming convention to express the version of the underlying artifacts could be usefull. The current issue will be the same for other artifact so it will be great to have a official way of express it. For example in a well known distribution, the package ant has a version 1.6.5-6 It means that this is the revision 6 of the package for the same tools ant which has the version 1.6.5 It's the same thing with more complex version number : 0.11.1-1.2 by this way, it's easier to be up to date on the plugin without changing the underlying tool. ++ -- View this message in context: http://www.nabble.com/How-to-handle-different-tool-versions-in-Maven-plugins--tf2720891s177.html#a7599029 Sent from the Maven Developers mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
