> Apparently, this change would make custom lifecycle mappings that don't > specify plugin versions subject to automatic plugin version resolution as in > Maven 2.0.8- unless the consuming POM (or its parents) locked the version > down. On the hand, Maven 3 will report this situation as a prominent warning > and we preach locking down plugin versions for some time now.
At first blush I think this is in the right direction, but I have a few thoughts that I want to throw out: 1) we included some plugins that are commonly used but aren't in a lifecycle such as the dependency and enforcer plugins. 2) what are the impacts to the plugin when it's run in multiple lifecycles, or if the user binds it to a phase of some other lifecycle? Would this cause the version to vary in unpredictable ways? 3) what is the impact to direct cli invocation now? --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
