Yes, it should be inherited. It's already in JIRA for 2.0.5.
- Brett
On 18/07/2006 7:22 AM, Brian E. Fox wrote:
I would like to see this, in fact I think I wrote a jira about it. We're
trying to ensure that our entire dev team is using a consistent maven
version. The obvious way to do this is to add it to our own super-pom
but that doesn't work. I ended up creating an empty plugin with a
prereq, but it feels kinda wonky to need that.
If you are saying in a parent pom that a prereq is needed, why wouldn't
a child project also have that prereq? If it wasn't intended to apply to
all children, then you would just put it in the children that do have
the prereq....just like you do with dependencies. I guess I just don't
see why this would be any different than anything else in the pom.
-----Original Message-----
From: Edwin Punzalan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 28, 2006 8:18 PM
To: Maven Developers List
Subject: add <prerequisites> in plugin parent pom
Now that we're starting to *properly* document plugins and
<prerequisites> is now a required pom element, I think that it a default
should be placed in the plugin-parent pom.xml.
However, <prerequisites> is not an inherited pom element so I'd like to
ask if allowing <prerequisites> to be inherited is also a good idea?
---------------------------------------------------------------------
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]
--
Apache Maven - http://maven.apache.org/
Better Builds with Maven - http://library.mergere.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
