You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by Emmanuel Venisse <em...@venisse.net> on 2004/09/06 18:55:25 UTC
inheritance problem when pom.xml exists in ~/.m2
Hi Brett,
Since you add a pom file for user, we have some inheritence problem.
If ~/.m2/pom.xml exists, some pom tags are ignored like type. If I remove
the pom file, all works fine.
With this pom.xml, I obtain a jar type for all my artifact, so I can't
build/install plugins project.
Emmanuel
Re: inheritance problem when pom.xml exists in ~/.m2
Posted by Trygve Laugstøl <tr...@apache.org>.
On Tue, Sep 07, 2004 at 10:09:17AM +0200, Emmanuel Venisse wrote:
>
> ----- Original Message -----
> From: "Brett Porter" <br...@apache.org>
> To: "Maven 2 Developers List" <m2...@maven.apache.org>
> Sent: Tuesday, September 07, 2004 1:18 AM
> Subject: Re: inheritance problem when pom.xml exists in ~/.m2
>
>
> > I think that is more to do with your change to inherit type (which
> > happened after my changes).
> >
> > I don't think that the type should be inherited.
>
> I removed all my changes in local and I have always the problems.
> Why you don't want inherit the type? For example, if you develop only
> plugins or war, it's more simple to write a super pom that define the
> type.
Because the super pom itself is a project and should possibly have it's
own type to indicate that it is a abstract pom. The CLI might be made to
take a look at the type and start a reactor run over all subprojects. It's
also very useful for report generation to know that this is a abstract
project.
This is something Jason and I discussed but I'm not sure what we decided.
--
Trygve
>
> Emmanuel
>
> >
> > - Brett
> >
> > Quoting Emmanuel Venisse <em...@venisse.net>:
> >
> > > Hi Brett,
> > >
> > > Since you add a pom file for user, we have some inheritence problem.
> > > If ~/.m2/pom.xml exists, some pom tags are ignored like type. If I remove
> > > the pom file, all works fine.
> > > With this pom.xml, I obtain a jar type for all my artifact, so I can't
> > > build/install plugins project.
> > >
> > > Emmanuel
> > >
Re: inheritance problem when pom.xml exists in ~/.m2
Posted by Emmanuel Venisse <em...@venisse.net>.
It's fixed. It was due to user pom loading, it have a default type define to
jar and overrite the type define in the pom project.
Emmanuel
----- Original Message -----
From: "Emmanuel Venisse" <em...@venisse.net>
To: "Maven 2 Developers List" <m2...@maven.apache.org>
Sent: Tuesday, September 07, 2004 10:09 AM
Subject: Re: inheritance problem when pom.xml exists in ~/.m2
>
> ----- Original Message -----
> From: "Brett Porter" <br...@apache.org>
> To: "Maven 2 Developers List" <m2...@maven.apache.org>
> Sent: Tuesday, September 07, 2004 1:18 AM
> Subject: Re: inheritance problem when pom.xml exists in ~/.m2
>
>
> > I think that is more to do with your change to inherit type (which
> happened
> > after my changes).
> >
> > I don't think that the type should be inherited.
>
> I removed all my changes in local and I have always the problems.
> Why you don't want inherit the type? For example, if you develop only
> plugins or war, it's more simple to write a super pom that define the
type.
>
> Emmanuel
>
> >
> > - Brett
> >
> > Quoting Emmanuel Venisse <em...@venisse.net>:
> >
> > > Hi Brett,
> > >
> > > Since you add a pom file for user, we have some inheritence problem.
> > > If ~/.m2/pom.xml exists, some pom tags are ignored like type. If I
> remove
> > > the pom file, all works fine.
> > > With this pom.xml, I obtain a jar type for all my artifact, so I can't
> > > build/install plugins project.
> > >
> > > Emmanuel
> > >
> >
> >
> >
>
>
Re: inheritance problem when pom.xml exists in ~/.m2
Posted by Emmanuel Venisse <em...@venisse.net>.
----- Original Message -----
From: "Brett Porter" <br...@apache.org>
To: "Maven 2 Developers List" <m2...@maven.apache.org>
Sent: Tuesday, September 07, 2004 1:18 AM
Subject: Re: inheritance problem when pom.xml exists in ~/.m2
> I think that is more to do with your change to inherit type (which
happened
> after my changes).
>
> I don't think that the type should be inherited.
I removed all my changes in local and I have always the problems.
Why you don't want inherit the type? For example, if you develop only
plugins or war, it's more simple to write a super pom that define the type.
Emmanuel
>
> - Brett
>
> Quoting Emmanuel Venisse <em...@venisse.net>:
>
> > Hi Brett,
> >
> > Since you add a pom file for user, we have some inheritence problem.
> > If ~/.m2/pom.xml exists, some pom tags are ignored like type. If I
remove
> > the pom file, all works fine.
> > With this pom.xml, I obtain a jar type for all my artifact, so I can't
> > build/install plugins project.
> >
> > Emmanuel
> >
>
>
>
Re: inheritance problem when pom.xml exists in ~/.m2
Posted by Brett Porter <br...@apache.org>.
I think that is more to do with your change to inherit type (which happened
after my changes).
I don't think that the type should be inherited.
- Brett
Quoting Emmanuel Venisse <em...@venisse.net>:
> Hi Brett,
>
> Since you add a pom file for user, we have some inheritence problem.
> If ~/.m2/pom.xml exists, some pom tags are ignored like type. If I remove
> the pom file, all works fine.
> With this pom.xml, I obtain a jar type for all my artifact, so I can't
> build/install plugins project.
>
> Emmanuel
>