> [ ] (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
B. The release plugin should lock version numbers down as part of the release process and then the build is repeatable. For development builds I am happy to either manually specify plugin values (to workaround defects) or use whatever is located in my local repository or occassionally run -cpu -U to pull down a newever version. There is nothing stopping someone who wants more formalism to lock their poms down themselves (maybe with the help of a tool) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
