On 9/1/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)
Given my answer to the other poll, that I don't mind maintaining a big <pluginManagement> section in a corporate parent pom... I think I have to go with B here so that new users can do things like play with the quickstart archetype without being exposed to a hundred lines of plugin config. If that poll comes out in favor of plugin packs or mixins... then I'll happily take A here. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
