AFAIK the <plugins> section is inherited by modules, and the <pluginmanagement> only defines a common configuration for plugins BUT does not enable them on child modules.
You can then configure commons plugin for all your modules in <plugins> and define a common configuration for some plugin that are only used in some modules (but not all). Those module will then only add a <plugin> entry with no configuration. Nico. 2006/12/4, CodingPlayer <[EMAIL PROTECTED]>:
Hi, i just found out about the existence of the <pluginManagement> section in a pom.xml. But i wonder, what is the difference to a <plugin> section?? Until now, i only use a <plugin> section in my parent pom.xml, and all of the plugins still work in my sub-projects. So, why should i put these plugins under the <pluginManagement> section? thx 4 help R.C. -- View this message in context: http://www.nabble.com/-M2--%3CpluginManagement%3E-vs.-%3Cplugin%3E-in-parent-pom.xml-tf2754489s177.html#a7680557 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
