On Nov 13, 2008, at 10:40 AM, Nick Stolwijk wrote:
Yes, take a look at multi module builds. The pluginManagement section
will be valid for all child modules instead of only this module.
This does not seem to be true. In the Chapter 6 example, if you remove
the pluginManagement section, leavi
This one too :
http://blogs.sonatype.com/people/brian/2008/05/26/optimal-maven-plugin-c
onfiguration/
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2008 10:42 AM
To: Maven Users List
Subject: RE: Why is pluginManagement necessary?
Trevor
On Thursday 13 November 2008 Trevor Harmon wrote:
> I'm really confused about the pluginManagement section. It seems
> arbitrary and unnecessary.
is for what is for
. is best explained in this thread:
http://www.nabble.com/What's-the-defference-between-the-dependencyManagement-and-dependencie
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 PROTEC
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"
This is the best explanation that I was able to find:
http://maven.apache.org/pom.html#Plugin_Management
---
Todd Thiessen
-Original Message-
From: Trevor Harmon [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 13, 2008 10:30 AM
To: Maven Users List
Subject: Why is
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:
org.apache.maven.plugins
maven
