Yes, take a look at multi module builds. The pluginManagement section will be valid for all child modules instead of only this module.
Hth, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Thu, Nov 13, 2008 at 4:29 PM, Trevor Harmon <[EMAIL PROTECTED]> wrote: > 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]
