It all depends on what you want to accomplish. Configuration in pluginMgmt will be used if you execute the plugin goal specifically from CLI (like "mvn plugin:goal"). So one use case to have move the configuration to the pluginMgmt section would be if you want to have some config for the build AND for when executing the plugin goal directly.
And some people like defining the version of plugins in the pluginMgmt section but not in build/plugins. Then you define this in a parent and only have one place to change when new versions are released. This is how I do it. /Anders On Sat, Sep 10, 2011 at 02:14, sebb <[email protected]> wrote: > AIUI, both build/plugins and build/pluginManagement are inherited by > child projects, the difference being that plugiManagement entries are > only used if the child project references the plugin in its > build/plugins section. > > That being the case, if a plugin is defined in build/plugins, is there > any point also including it in the build/pluginManagement/plugins > section? > > --------------------------------------------------------------------- > 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]
