You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Adrian Herscu <bm...@fastmail.fm> on 2007/05/15 16:32:52 UTC
[m2.0.6] seems like a classloader issue...
Hi all,
In a multi-project P, child #1 (cP1) runs before child #2 (cP2).
In cP1 the build uses the maven-antrun-plugin:1.1 and in cP2 the build
uses maven-antrun-plugin:1.1-INTERNAL (which patches version of 1.1 in
order to use ant-1.7.0 instead of ant-1.6.5).
When running mvn install on P, the cP1 builds normally, but the cP2
fails because it uses the maven-antrun-plugin:1.1 instead of
maven-antrun-plugin:1.1-INTERNAL :-(
If I change cP1 to use maven-antrun-plugin:1.1-INTERNAL, with all the
dependencies from cP2, then everything works fine!
Adrian.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2.0.6] seems like a classloader issue...
Posted by Wayne Fay <wa...@gmail.com>.
Feel free to file a bug/RFE for 2.0.x or add it to the 2.1.x
"requested features" list in the Wiki. I agree that this should work,
generally.
Wayne
On 5/15/07, Adrian Herscu <bm...@fastmail.fm> wrote:
> Very sad... Plexus... Forehead... Bunches of classloaders... and still
> it cannot use different versions of plugins...
>
> Max Bowsher wrote:
> > Adrian Herscu wrote:
> >> Hi all,
> >>
> >> In a multi-project P, child #1 (cP1) runs before child #2 (cP2).
> >>
> >> In cP1 the build uses the maven-antrun-plugin:1.1 and in cP2 the build
> >> uses maven-antrun-plugin:1.1-INTERNAL (which patches version of 1.1 in
> >> order to use ant-1.7.0 instead of ant-1.6.5).
> >>
> >> When running mvn install on P, the cP1 builds normally, but the cP2
> >> fails because it uses the maven-antrun-plugin:1.1 instead of
> >> maven-antrun-plugin:1.1-INTERNAL :-(
> >>
> >> If I change cP1 to use maven-antrun-plugin:1.1-INTERNAL, with all the
> >> dependencies from cP2, then everything works fine!
> >
> > Sadly, Maven doesn't seem to be able to cope with using different
> > versions of a plugin in different projects within a multi-project build.
> > It just uses the first it encountered within the built.
> >
> > Max.
> >
> >
>
>
> ---------------------------------------------------------------------
> 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: [m2.0.6] seems like a classloader issue...
Posted by Adrian Herscu <bm...@fastmail.fm>.
Very sad... Plexus... Forehead... Bunches of classloaders... and still
it cannot use different versions of plugins...
Max Bowsher wrote:
> Adrian Herscu wrote:
>> Hi all,
>>
>> In a multi-project P, child #1 (cP1) runs before child #2 (cP2).
>>
>> In cP1 the build uses the maven-antrun-plugin:1.1 and in cP2 the build
>> uses maven-antrun-plugin:1.1-INTERNAL (which patches version of 1.1 in
>> order to use ant-1.7.0 instead of ant-1.6.5).
>>
>> When running mvn install on P, the cP1 builds normally, but the cP2
>> fails because it uses the maven-antrun-plugin:1.1 instead of
>> maven-antrun-plugin:1.1-INTERNAL :-(
>>
>> If I change cP1 to use maven-antrun-plugin:1.1-INTERNAL, with all the
>> dependencies from cP2, then everything works fine!
>
> Sadly, Maven doesn't seem to be able to cope with using different
> versions of a plugin in different projects within a multi-project build.
> It just uses the first it encountered within the built.
>
> Max.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2.0.6] seems like a classloader issue...
Posted by Max Bowsher <ma...@ukf.net>.
Adrian Herscu wrote:
> Hi all,
>
> In a multi-project P, child #1 (cP1) runs before child #2 (cP2).
>
> In cP1 the build uses the maven-antrun-plugin:1.1 and in cP2 the build
> uses maven-antrun-plugin:1.1-INTERNAL (which patches version of 1.1 in
> order to use ant-1.7.0 instead of ant-1.6.5).
>
> When running mvn install on P, the cP1 builds normally, but the cP2
> fails because it uses the maven-antrun-plugin:1.1 instead of
> maven-antrun-plugin:1.1-INTERNAL :-(
>
> If I change cP1 to use maven-antrun-plugin:1.1-INTERNAL, with all the
> dependencies from cP2, then everything works fine!
Sadly, Maven doesn't seem to be able to cope with using different
versions of a plugin in different projects within a multi-project build.
It just uses the first it encountered within the built.
Max.
Re: [m2.0.6] seems like a classloader issue...
Posted by Wayne Fay <wa...@gmail.com>.
Try locking the version in both projects using
<version>[1.1]</version> etc. Otherwise Maven might decide to use one
version (or the other) for both builds, despite the different
declarations.
Wayne
On 5/15/07, Adrian Herscu <bm...@fastmail.fm> wrote:
> Hi all,
>
> In a multi-project P, child #1 (cP1) runs before child #2 (cP2).
>
> In cP1 the build uses the maven-antrun-plugin:1.1 and in cP2 the build
> uses maven-antrun-plugin:1.1-INTERNAL (which patches version of 1.1 in
> order to use ant-1.7.0 instead of ant-1.6.5).
>
> When running mvn install on P, the cP1 builds normally, but the cP2
> fails because it uses the maven-antrun-plugin:1.1 instead of
> maven-antrun-plugin:1.1-INTERNAL :-(
>
> If I change cP1 to use maven-antrun-plugin:1.1-INTERNAL, with all the
> dependencies from cP2, then everything works fine!
>
> Adrian.
>
>
> ---------------------------------------------------------------------
> 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