maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject RE: project inheritence
Date Mon, 29 Sep 2003 03:22:44 GMT
maven.xml already gets run as well. My latest work not only clears up
inheritence for project.xml but also loads parent I
think. I haven't tested that far yet as I am clearing up other issues with
it. This needs more discussion as dIon and I disagree on what exactly should
be inherited.

As Jason's post the other day said too, was that the new component based
version of Maven will more clearly define the rules for this.

- Brett

> -----Original Message-----
> From: Nathan Coast [] 
> Sent: Monday, 29 September 2003 12:43 PM
> To: Maven Dev
> Subject: project inheritence
> Hi,
> I'd just like to clarify what the current state of play is 
> with project 
> inheritence and where the eventual goal is.
> I think there are 3 artifacts which could sensibly be inherited.
> project.xml / POM
> maven.xml
> I remember reading in a post from Jason that eventually all 
> three will inherit 
> fully with each subproject having the ability to override 
> anything set in the 
> parent artifact  - can't find the post.  AFAICT the current 
> state of play is 
> that only project.xml inherits (with build dependencies being 
> additive).  Is 
> this right?
> I know everyone is pretty busy working towards RC1.  What 
> sort of priority is 
> this work?
> there are also a number of relevant issues in Jira 
>> ?key=MAVEN-301
and probably quite a few more


To unsubscribe, e-mail:
For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message