> Now you're confusing me again. > You say - below - that CLI (goal) invocations ignore the build/plugins > settings. > > If so, then surely it's better to define everything in pluginMgmt, and > just leave the build/plugins section to reference the plugin? > > In which case both goal and phase invocations share the settings. > > Otherwise CLI(goal) invocations might not be fully configured.
Well, very often you're not going to execute the plugin goal directly from CLI. I'd say that most often you're not. It's like when coding, to implement stuff you don't currently need. It just makes things more complicated. /Anders > >>> The pluginManagement settings will I assume apply to all CLI (i.e. >>> goal) invocations. >> >> Yes, if you add the config on the plugin level and not on a specific >> execution. >> >>> This is presumably because individual goal invocation is not part of a >>> phase and so ignores what is in build/plugins >> >> Right, and this has tricked a lot of new Maven users. >> >> /Anders >> >>> >>>> But this is me. Others may very well have a different opinion. >>>> >>>> /Anders >>>> >>>>> >>>>>> /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] >>>>>> >>>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>>> 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] >> >> > > --------------------------------------------------------------------- > 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]
