So maybe we should publish far and wide the best practice of pegging the plugin version, and require it in 2.1...then write a plugin to list the available versions for a plugin, so users can check periodically. That would make life a little easier for users.
-j On 4/10/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 10 Apr 07, at 12:42 PM 10 Apr 07, Brian E. Fox wrote: > "This is a MUCH bigger problem than we seem to recognize. Who > wants to > send the email to the users@ list to tell them that, oh, yeah, they > need > to specify versions for all of their plugins in the POM? I'm not wild > about it, but I think that's the only way out...and I'm willing to > send > that email." > We can't do this in 2.0.x but it needs to be mandatory in 2.1. > We recently discussed this on this list (maybe even related to > Assembly...no it was Brett's proposal for a separate Alpha repo). > If we > are to encourage best practices, then we really should encourage the > plugin versions to be set in the poms or pluginManagement. I would > even > assert that it should be required in 2.1 as it is for dependenceis > now. Yes, otherwise there is no deterministic way to know what version of a plugin was used. You can look in the local repo and look for the latest version but that's no guarantee either. It needs to be as structured as versions for any dependency. As I noted before the onus is on us to make it easy to select the latest version but everything needs to be versioned. The magic latest release lookup has not been a boon IMO. Jason. > No build team who is concerned about reproducibility would really > allow > the versions to be uncontrolled and entirely up to the developers > environment. (If they are, maybe they don't realize this is occuring). > > --------------------------------------------------------------------- > 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]
