Trevor, This will help: http://blogs.sonatype.com/people/brian/2008/04/10/maven-209-released/ And chapter 8 in the book also talks about how to use pluginMgt more effectively: http://www.sonatype.com/book/reference/optimizing.html
-----Original Message----- From: Trevor Harmon [mailto:[EMAIL PROTECTED] Sent: Thursday, November 13, 2008 10:30 AM To: Maven Users List Subject: Why is pluginManagement necessary? I'm really confused about the pluginManagement section. It seems arbitrary and unnecessary. For instance, in the Chapter 6 example from "Maven: The Definitive Guide", there is the following declaration: <build> <pluginManagement> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> </configuration> </plugin> </plugins> </pluginManagement> </build> Without this declaration, the project fails to compile because the source code uses Java 1.5 syntax. However -- and this is the part that baffles me -- if you simply remove the pluginManagement tags (leaving the plugins section intact), it still works perfectly! Can someone point me to an example where pluginManagement actually serves a purpose? Thanks, Trevor --------------------------------------------------------------------- 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]
