> So the CLI case ignores anything in build/plugins? Yes.
> What about CLI invocation of report plugins? > Can they inherit from anywhere? I don't think so. This has been one of the limitations wrt reporting plugins. >> 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. > I take it you mean the plugin entry in build/plugins would then just > contain the groupId/artifactId. Yes, and the execution declaration. /Anders > >> 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. > > Yes, that is mainly how it is being used. > >> /Anders > > Thanks! > >> 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] >> >> > > --------------------------------------------------------------------- > 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]
