You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Erlend Hamnaberg <ng...@gmail.com> on 2009/12/04 13:03:29 UTC
maven 3 inheritance
Hi.
I am testing out maven 3 on our project.
I heard from Jason's presentation on JavaZone that you are supposed to be
able to have versionless parent elements.
Trying to build the attached project, makes it fail.
In maven 2 we could inherit properties, this doesn't seem to work anymore.
Can someone please take a look at the attached project, and tell me what I'm
doing wrong?
Best Regards
Erlend
Re: maven 3 inheritance
Posted by Stephen Connolly <st...@gmail.com>.
Using properties to specify dependency versions (for dependencies external
to the reactor) works fine with maven 3.0-alpha-5.
I cannot comment on using ${project.version} as it's bad practice (AFAIK,
although the release plugin has some code to "make" it work, IIRC the code
takes longer to run a build) so none of my projects use that
Also what is your issue with the release plugin... it's quite flexible and
should cover most cases (providing you tweak the release profile)... and if
your versioning scheme does not work with the release plugin, then EITHER
your scheme is a pile of sh1t and will lead you in to problems when used
with Maven OR we need to know about your wonderful near perfect scheme and
add support to the release plugin.
;-)
-Stephen
2009/12/9 Erlend Hamnaberg <ng...@gmail.com>
> I know it works for maven 2, however it seems broken for maven 3. I am
> going
> to test this a bit more, and report back.
> This might be a symptom of something else.
>
> I have also made expressions work for parent versions using a modified
> install & deploy plugin. I was hoping this would not be necessary in maven
> 3.
>
> We have multiple products which are build independently, but some of them
> have dependencies on each other. We do not want to have to specify the
> version for every product everywhere we use that, as it simply doesn't
> scale.
>
> We do not use the release plugin, as our versioning setup does not match
> how
> the release plugin works, and we don't want to modify YET another plugin
> just to make this broken plugin work.
>
> --Erlend
>
> On Wed, Dec 9, 2009 at 8:29 AM, Baptiste MATHUS <ml...@batmat.net> wrote:
>
> > And by the way, using variables for specifying dependencies versions
> > perfectly work out of the box with maven2.
> >
> > For example, we have a whole project hierarchy of 20+ modules that all
> have
> > the same version. Each module always references the parent version since
> it
> > must be there. But it doesn't have its own <version> tag, or even
> > <groupId>.
> > And referencing between modules is then just done by the standard
> variable
> > ${project.version}.
> >
> > FWIW.
> > Cheers.
> >
> > 2009/12/9 Paul Benedict <pb...@apache.org>
> >
> > > Dana, just to clarify, he was asking about variables in dependencies.
> > > I don't think the parent is considered a <dependency> in the technical
> > > sense that Maven uses.
> > >
> > > On Tue, Dec 8, 2009 at 6:40 PM, Lacoste, Dana (TSG Software San Diego)
> > > <da...@hp.com> wrote:
> > > > No, with maven 2 you cannot have a variable in the parent version.
> The
> > > string will be interpreted literally without dereferencing the variable
> > > name.
> > > >
> > > > Similarly, you can't have an empty version number: the parent MUST
> have
> > a
> > > defined version number and it MUST be absolute and not contain any
> > > variables.
> > > >
> > > > variables work fine in any other version number, however. ranges, on
> > the
> > > other hand, do not ;)
> > > >
> > > > Dana Lacoste
> > > >
> > > > -----Original Message-----
> > > > From: paulus.benedictus@gmail.com [mailto:
> paulus.benedictus@gmail.com]
> > > On Behalf Of Paul Benedict
> > > > Sent: Tuesday, December 08, 2009 4:37 PM
> > > > To: Maven Users List
> > > > Subject: Re: maven 3 inheritance
> > > >
> > > >> ...and parent versions?
> > > >
> > > > Good question. You'll have to find out if the project hierarchy or
> > > > dependency resolution is processed first. Report back and tell us!
> > > >
> > > > Paul
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> >
>
Re: maven 3 inheritance
Posted by Erlend Hamnaberg <ng...@gmail.com>.
I know it works for maven 2, however it seems broken for maven 3. I am going
to test this a bit more, and report back.
This might be a symptom of something else.
I have also made expressions work for parent versions using a modified
install & deploy plugin. I was hoping this would not be necessary in maven
3.
We have multiple products which are build independently, but some of them
have dependencies on each other. We do not want to have to specify the
version for every product everywhere we use that, as it simply doesn't
scale.
We do not use the release plugin, as our versioning setup does not match how
the release plugin works, and we don't want to modify YET another plugin
just to make this broken plugin work.
--Erlend
On Wed, Dec 9, 2009 at 8:29 AM, Baptiste MATHUS <ml...@batmat.net> wrote:
> And by the way, using variables for specifying dependencies versions
> perfectly work out of the box with maven2.
>
> For example, we have a whole project hierarchy of 20+ modules that all have
> the same version. Each module always references the parent version since it
> must be there. But it doesn't have its own <version> tag, or even
> <groupId>.
> And referencing between modules is then just done by the standard variable
> ${project.version}.
>
> FWIW.
> Cheers.
>
> 2009/12/9 Paul Benedict <pb...@apache.org>
>
> > Dana, just to clarify, he was asking about variables in dependencies.
> > I don't think the parent is considered a <dependency> in the technical
> > sense that Maven uses.
> >
> > On Tue, Dec 8, 2009 at 6:40 PM, Lacoste, Dana (TSG Software San Diego)
> > <da...@hp.com> wrote:
> > > No, with maven 2 you cannot have a variable in the parent version. The
> > string will be interpreted literally without dereferencing the variable
> > name.
> > >
> > > Similarly, you can't have an empty version number: the parent MUST have
> a
> > defined version number and it MUST be absolute and not contain any
> > variables.
> > >
> > > variables work fine in any other version number, however. ranges, on
> the
> > other hand, do not ;)
> > >
> > > Dana Lacoste
> > >
> > > -----Original Message-----
> > > From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
> > On Behalf Of Paul Benedict
> > > Sent: Tuesday, December 08, 2009 4:37 PM
> > > To: Maven Users List
> > > Subject: Re: maven 3 inheritance
> > >
> > >> ...and parent versions?
> > >
> > > Good question. You'll have to find out if the project hierarchy or
> > > dependency resolution is processed first. Report back and tell us!
> > >
> > > Paul
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
Re: maven 3 inheritance
Posted by Frederic Camblor <fc...@gmail.com>.
+1 with Stephen
We faced the problem with release plugin and, since then, are "hard coding"
version in the artefacts.
Frederic
On Wed, Dec 9, 2009 at 9:03 AM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> AFAIK using ${project.versopm} is not the preferred way. The release
> plugin
> will update all those versions for you so that you don't have to use
> ${project.version}. If you use ${project.version} then releases will be
> slower AFAIK due to some strange resolving issue!
>
> The use of properties for specifying versions in dependencies is usually
> when you want to lock a suite of dependencies (built externally to your
> reactor) to the same version, e.g.
>
> <properties>
> <jetty-version>6.1.20</jetty-version>
> </properties>
>
> <dependencies>
> <dependency>
> <groupId>org.mortbay.jetty</groupId>
> <artifactId>jetty</artifactId>
> <version>${jetty-version}</version>
> </dependency>
>
> <dependency>
> <groupId>org.mortbay.jetty</groupId>
> <artifactId>jetty-management</artifactId>
> <version>${jetty-version}</version>
> </dependency>
>
> <dependency>
> <groupId>org.mortbay.jetty</groupId>
> <artifactId>jetty-naming</artifactId>
> <version>${jetty-version}</version>
> </dependency>
>
> <dependency>
> <groupId>org.mortbay.jetty</groupId>
> <artifactId>jetty-plus</artifactId>
> <version>${jetty-version}</version>
> </dependency>
>
> <dependency>
> <groupId>org.mortbay.jetty</groupId>
> <artifactId>jetty-util</artifactId>
> <version>${jetty-version}</version>
> </dependency>
> </dependencies>
>
> in the above example, a property is the only way to ensure that all the
> dependencies are tied to the same version. In addition, if you have a pom
> with such a set of dependencies / dependencyManagement and the property is
> defined in the same pom.xml, then versions:update-properties becomes very
> handy
>
> -Stephen
>
> 2009/12/9 Baptiste MATHUS <ml...@batmat.net>
>
> > And by the way, using variables for specifying dependencies versions
> > perfectly work out of the box with maven2.
> >
> > For example, we have a whole project hierarchy of 20+ modules that all
> have
> > the same version. Each module always references the parent version since
> it
> > must be there. But it doesn't have its own <version> tag, or even
> > <groupId>.
> > And referencing between modules is then just done by the standard
> variable
> > ${project.version}.
> >
> > FWIW.
> > Cheers.
> >
> > 2009/12/9 Paul Benedict <pb...@apache.org>
> >
> > > Dana, just to clarify, he was asking about variables in dependencies.
> > > I don't think the parent is considered a <dependency> in the technical
> > > sense that Maven uses.
> > >
> > > On Tue, Dec 8, 2009 at 6:40 PM, Lacoste, Dana (TSG Software San Diego)
> > > <da...@hp.com> wrote:
> > > > No, with maven 2 you cannot have a variable in the parent version.
> The
> > > string will be interpreted literally without dereferencing the variable
> > > name.
> > > >
> > > > Similarly, you can't have an empty version number: the parent MUST
> have
> > a
> > > defined version number and it MUST be absolute and not contain any
> > > variables.
> > > >
> > > > variables work fine in any other version number, however. ranges, on
> > the
> > > other hand, do not ;)
> > > >
> > > > Dana Lacoste
> > > >
> > > > -----Original Message-----
> > > > From: paulus.benedictus@gmail.com [mailto:
> paulus.benedictus@gmail.com]
> > > On Behalf Of Paul Benedict
> > > > Sent: Tuesday, December 08, 2009 4:37 PM
> > > > To: Maven Users List
> > > > Subject: Re: maven 3 inheritance
> > > >
> > > >> ...and parent versions?
> > > >
> > > > Good question. You'll have to find out if the project hierarchy or
> > > > dependency resolution is processed first. Report back and tell us!
> > > >
> > > > Paul
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > Baptiste <Batmat> MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> >
>
Re: maven 3 inheritance
Posted by Stephen Connolly <st...@gmail.com>.
AFAIK using ${project.versopm} is not the preferred way. The release plugin
will update all those versions for you so that you don't have to use
${project.version}. If you use ${project.version} then releases will be
slower AFAIK due to some strange resolving issue!
The use of properties for specifying versions in dependencies is usually
when you want to lock a suite of dependencies (built externally to your
reactor) to the same version, e.g.
<properties>
<jetty-version>6.1.20</jetty-version>
</properties>
<dependencies>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty</artifactId>
<version>${jetty-version}</version>
</dependency>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-management</artifactId>
<version>${jetty-version}</version>
</dependency>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-naming</artifactId>
<version>${jetty-version}</version>
</dependency>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-plus</artifactId>
<version>${jetty-version}</version>
</dependency>
<dependency>
<groupId>org.mortbay.jetty</groupId>
<artifactId>jetty-util</artifactId>
<version>${jetty-version}</version>
</dependency>
</dependencies>
in the above example, a property is the only way to ensure that all the
dependencies are tied to the same version. In addition, if you have a pom
with such a set of dependencies / dependencyManagement and the property is
defined in the same pom.xml, then versions:update-properties becomes very
handy
-Stephen
2009/12/9 Baptiste MATHUS <ml...@batmat.net>
> And by the way, using variables for specifying dependencies versions
> perfectly work out of the box with maven2.
>
> For example, we have a whole project hierarchy of 20+ modules that all have
> the same version. Each module always references the parent version since it
> must be there. But it doesn't have its own <version> tag, or even
> <groupId>.
> And referencing between modules is then just done by the standard variable
> ${project.version}.
>
> FWIW.
> Cheers.
>
> 2009/12/9 Paul Benedict <pb...@apache.org>
>
> > Dana, just to clarify, he was asking about variables in dependencies.
> > I don't think the parent is considered a <dependency> in the technical
> > sense that Maven uses.
> >
> > On Tue, Dec 8, 2009 at 6:40 PM, Lacoste, Dana (TSG Software San Diego)
> > <da...@hp.com> wrote:
> > > No, with maven 2 you cannot have a variable in the parent version. The
> > string will be interpreted literally without dereferencing the variable
> > name.
> > >
> > > Similarly, you can't have an empty version number: the parent MUST have
> a
> > defined version number and it MUST be absolute and not contain any
> > variables.
> > >
> > > variables work fine in any other version number, however. ranges, on
> the
> > other hand, do not ;)
> > >
> > > Dana Lacoste
> > >
> > > -----Original Message-----
> > > From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
> > On Behalf Of Paul Benedict
> > > Sent: Tuesday, December 08, 2009 4:37 PM
> > > To: Maven Users List
> > > Subject: Re: maven 3 inheritance
> > >
> > >> ...and parent versions?
> > >
> > > Good question. You'll have to find out if the project hierarchy or
> > > dependency resolution is processed first. Report back and tell us!
> > >
> > > Paul
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Baptiste <Batmat> MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
Re: maven 3 inheritance
Posted by Baptiste MATHUS <ml...@batmat.net>.
And by the way, using variables for specifying dependencies versions
perfectly work out of the box with maven2.
For example, we have a whole project hierarchy of 20+ modules that all have
the same version. Each module always references the parent version since it
must be there. But it doesn't have its own <version> tag, or even <groupId>.
And referencing between modules is then just done by the standard variable
${project.version}.
FWIW.
Cheers.
2009/12/9 Paul Benedict <pb...@apache.org>
> Dana, just to clarify, he was asking about variables in dependencies.
> I don't think the parent is considered a <dependency> in the technical
> sense that Maven uses.
>
> On Tue, Dec 8, 2009 at 6:40 PM, Lacoste, Dana (TSG Software San Diego)
> <da...@hp.com> wrote:
> > No, with maven 2 you cannot have a variable in the parent version. The
> string will be interpreted literally without dereferencing the variable
> name.
> >
> > Similarly, you can't have an empty version number: the parent MUST have a
> defined version number and it MUST be absolute and not contain any
> variables.
> >
> > variables work fine in any other version number, however. ranges, on the
> other hand, do not ;)
> >
> > Dana Lacoste
> >
> > -----Original Message-----
> > From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com]
> On Behalf Of Paul Benedict
> > Sent: Tuesday, December 08, 2009 4:37 PM
> > To: Maven Users List
> > Subject: Re: maven 3 inheritance
> >
> >> ...and parent versions?
> >
> > Good question. You'll have to find out if the project hierarchy or
> > dependency resolution is processed first. Report back and tell us!
> >
> > Paul
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
Re: maven 3 inheritance
Posted by Paul Benedict <pb...@apache.org>.
Dana, just to clarify, he was asking about variables in dependencies.
I don't think the parent is considered a <dependency> in the technical
sense that Maven uses.
On Tue, Dec 8, 2009 at 6:40 PM, Lacoste, Dana (TSG Software San Diego)
<da...@hp.com> wrote:
> No, with maven 2 you cannot have a variable in the parent version. The string will be interpreted literally without dereferencing the variable name.
>
> Similarly, you can't have an empty version number: the parent MUST have a defined version number and it MUST be absolute and not contain any variables.
>
> variables work fine in any other version number, however. ranges, on the other hand, do not ;)
>
> Dana Lacoste
>
> -----Original Message-----
> From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com] On Behalf Of Paul Benedict
> Sent: Tuesday, December 08, 2009 4:37 PM
> To: Maven Users List
> Subject: Re: maven 3 inheritance
>
>> ...and parent versions?
>
> Good question. You'll have to find out if the project hierarchy or
> dependency resolution is processed first. Report back and tell us!
>
> Paul
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: maven 3 inheritance
Posted by "Lacoste, Dana (TSG Software San Diego)" <da...@hp.com>.
No, with maven 2 you cannot have a variable in the parent version. The string will be interpreted literally without dereferencing the variable name.
Similarly, you can't have an empty version number: the parent MUST have a defined version number and it MUST be absolute and not contain any variables.
variables work fine in any other version number, however. ranges, on the other hand, do not ;)
Dana Lacoste
-----Original Message-----
From: paulus.benedictus@gmail.com [mailto:paulus.benedictus@gmail.com] On Behalf Of Paul Benedict
Sent: Tuesday, December 08, 2009 4:37 PM
To: Maven Users List
Subject: Re: maven 3 inheritance
> ...and parent versions?
Good question. You'll have to find out if the project hierarchy or
dependency resolution is processed first. Report back and tell us!
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven 3 inheritance
Posted by Paul Benedict <pb...@apache.org>.
Erlend,
> is it then possible to use variables for dependency versions?
Yes. This is supported today in Maven 2.
> ...and parent versions?
Good question. You'll have to find out if the project hierarchy or
dependency resolution is processed first. Report back and tell us!
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven 3 inheritance
Posted by Erlend Hamnaberg <ng...@gmail.com>.
ok, thanks.
is it then possible to use variables for dependency versions and parent
versions?
The maven integration in IDEA and eclipse complains about this, and I'm
guessing that both of these use maven3 as the baseline.
This sort of works in maven2 (with modifications of install and deploy
plugins). I was hoping that this would work out of the box in maven 3.
-- Erlend
On Tue, Dec 8, 2009 at 10:51 PM, Paul Benedict <pb...@apache.org> wrote:
> Last I know, this is not yet implemented. The focus of Maven 3 alpha
> releases is backwards compatibility with Maven 2. New features have
> not yet been added.
>
> Paul
>
> On Tue, Dec 8, 2009 at 2:54 PM, Erlend Hamnaberg <ng...@gmail.com>
> wrote:
> > Noone?
> > Is this the wrong forum for maven 3 related questions?
> >
> > -- Erlennd
> >
> > On Fri, Dec 4, 2009 at 1:03 PM, Erlend Hamnaberg <ng...@gmail.com>
> wrote:
> >
> >> Hi.
> >>
> >> I am testing out maven 3 on our project.
> >> I heard from Jason's presentation on JavaZone that you are supposed to
> be
> >> able to have versionless parent elements.
> >> Trying to build the attached project, makes it fail.
> >>
> >> In maven 2 we could inherit properties, this doesn't seem to work
> anymore.
> >>
> >> Can someone please take a look at the attached project, and tell me what
> >> I'm doing wrong?
> >>
> >>
> >> Best Regards
> >>
> >> Erlend
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: maven 3 inheritance
Posted by Paul Benedict <pb...@apache.org>.
Last I know, this is not yet implemented. The focus of Maven 3 alpha
releases is backwards compatibility with Maven 2. New features have
not yet been added.
Paul
On Tue, Dec 8, 2009 at 2:54 PM, Erlend Hamnaberg <ng...@gmail.com> wrote:
> Noone?
> Is this the wrong forum for maven 3 related questions?
>
> -- Erlennd
>
> On Fri, Dec 4, 2009 at 1:03 PM, Erlend Hamnaberg <ng...@gmail.com> wrote:
>
>> Hi.
>>
>> I am testing out maven 3 on our project.
>> I heard from Jason's presentation on JavaZone that you are supposed to be
>> able to have versionless parent elements.
>> Trying to build the attached project, makes it fail.
>>
>> In maven 2 we could inherit properties, this doesn't seem to work anymore.
>>
>> Can someone please take a look at the attached project, and tell me what
>> I'm doing wrong?
>>
>>
>> Best Regards
>>
>> Erlend
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven 3 inheritance
Posted by Erlend Hamnaberg <ng...@gmail.com>.
Noone?
Is this the wrong forum for maven 3 related questions?
-- Erlennd
On Fri, Dec 4, 2009 at 1:03 PM, Erlend Hamnaberg <ng...@gmail.com> wrote:
> Hi.
>
> I am testing out maven 3 on our project.
> I heard from Jason's presentation on JavaZone that you are supposed to be
> able to have versionless parent elements.
> Trying to build the attached project, makes it fail.
>
> In maven 2 we could inherit properties, this doesn't seem to work anymore.
>
> Can someone please take a look at the attached project, and tell me what
> I'm doing wrong?
>
>
> Best Regards
>
> Erlend
>