Hi All, What extra things <pluginManagement> provides than using only <plugins>.
CASE 1: if I have a parent POM having few plugins in <pluginManagement> section ---> so the children POMs will be using same version of plugin as specified in <pluginManagement> and I do not even need to specify anything in my child POM, why is that ? Because the maven documentation<http://maven.apache.org/pom.html#Plugin_Management>says you need to add plugin entry in your child POM to use that plugin (specified in parent POM's pluginManagement section,). I thought I will add that plugin in child pom only if I want to change version. Line from the page : *"If we added these specifications to the plugins element, they would apply only to a single POM. However, if we apply them under the pluginManagement*element, then this POM *and all inheriting POMs that add the maven-jar-plugin to the build will get the pre-process-classes execution as well. So rather than the above mess included in every child pom.xml, only the following is required:* " CASE2: if I donot use <pluginManagement> and only use <plugins>: ---> In this case also I can get everything I want as above. All child pom gets the plugins define in parent pom without adding any entry. OS what's the difference? So whats the point in going for <pluginManagement>, Is it only to Enforce to use same version of plugin and provide some clarity to whole application (parent and child) or it is for more than these? Please provide some test case to understand the difference.. Thanks, Amaresh
