[A]. IMO this is totally critical to generate auditably correct builds, which ought to be the default. I've got 3 or 4 maven-built projects, and it's already a bit of a nightmare - I really really don't want to be in the situation where downloading new releases of mvn 'magically' updates plugins, or packs of plugins in the background.
There's plenty of things that could be done to stop the 'new user' experience being bad, such as adding default versions in the super-pom, adding interactive 'which version do you mean' questions for projects being updated and providing a mojo that updates all your POMs automatically; maybe even allowing commandline-specified invocations (like eclipse:eclipse) to default to the latest release. But a build tool that doesn't guarantee that the same inputs always produce the same ouputs on any given day without the need for 'special best practice plugins' to be used isn't a good place to be, IMO. On 02/09/07, Brett Porter <[EMAIL PROTECTED]> wrote: > > I'd like to hear from as many people as possible their opinion this > topic (even if you just want to say '0' so we know where you stand). > > [ ] (A) All plugin versions must be specified by the project or its > parent hierarchy somewhere, at the cost of some verbosity (though we > should look at ways to make this easier/smaller/etc per the current > discussion) > [ ] (B) Retain the current behaviour, but make using the enforcer a > best practice to do the above, or some other control mechanism such > as having the repository manager handle the available plugins > [ ] (C) No opinion > [ ] (D) Undecided > [ ] (E) Other (please specify) > > Thanks, > Brett > > -- > Brett Porter - [EMAIL PROTECTED] > Blog: http://www.devzuz.org/blogs/bporter/ > >
