Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
From: Jason van Zyl <jason@tesla.io>
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_6DA33727-1333-487F-814B-7AE1CE114CCA"
Subject: Re: Meta information about dependencies in a pom?
Date: Tue, 8 Nov 2011 21:00:42 -0800
In-Reply-To: 
 <CAKkCf4oWc9vk8E-ZfWfNLSJ0AoA400it2WudFHpUmEUy8N3mqQ@mail.gmail.com>
To: "Maven Developers List" <dev@maven.apache.org>
References: 
 <CAKkCf4ooFYCLfBO3nTLZO1pcGReAUx5Z+QFCSHsdsMdPA-hZkw@mail.gmail.com>
 <CAKkCf4oiD2DY8EUmT6E+6mEQxWPB5OmCa8qqLQ8eQeQAtcULeg@mail.gmail.com>
 <925685FD-5C8A-4093-870A-9A007E98687B@apache.org>
 <CAKkCf4qNRJWFeM3pywhJEiCJVbN2S8-FY+pY-uELUf9ujaw8TA@mail.gmail.com>
 <CABjrKuLpb=kdk=8FfqXCR9cOO+aML65PWsAnfhGs1h4HVXLD8A@mail.gmail.com>
 <CAKkCf4oWc9vk8E-ZfWfNLSJ0AoA400it2WudFHpUmEUy8N3mqQ@mail.gmail.com>
Message-Id: <CFA400F0-4C3B-44ED-9FAD-3733285AF682@tesla.io>

--Apple-Mail=_6DA33727-1333-487F-814B-7AE1CE114CCA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Nov 8, 2011, at 8:00 PM, Carsten Ziegeler wrote:

> 2011/11/8 Guo Du <mrduguo@duguo.org>:
>>> too error prone as you have to keep the plugin configuration and the
>>> dependency list in sync. It doesn't sound like a hard task first, =
but
>> What about only configure the dependency list with additional field =
as
>> plugin configuration such as:
>> <configuration>
>> <bundles>
>> <bundle>
>> <groupId>foo</groupId>
>> <artifactId>bar</artifactId>
>> <version>x.y.z</version>
>> <startLevel>1</startLevel>
>> </bundle>
>> </bundles>
>> </configuration>
>>=20
>>=20
> Yes, that's basically a variant of what we came up with, but in this
> case the dependencies are not considered when maven is calculating a
> build order for a multi project build, so you end up with a "wrong"
> order when you are using snapshot dependencies. We had cases where the
> snapshot dep was built after the assembly causing an old snapshop to
> end up in the application.
> And other plugins like the versions plugin don't see this either.
>=20
> But today we learned about the AbstractMavenLifecycleParticipant which
> hopefully allows us to use above configuration without the above
> problems.

Here's an example of how it works for matching the dependencies =
specified from a 3rd party source to the reactor.

=
https://github.com/etesla/proviso/tree/master/tesla-proviso-plugin/src/mai=
n/java/org/eclipse/tesla/plugins/proviso

It's using JSR330, but you can pull those out and use Plexus annotations =
if you need it to work in the short term.

>=20
> Regards
> Carsten
>=20
>> -Guo
>>=20
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>=20
>>=20
>=20
>=20
>=20
> --=20
> Carsten Ziegeler
> cziegeler@apache.org
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>=20

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
http://twitter.com/jvanzyl
---------------------------------------------------------


--Apple-Mail=_6DA33727-1333-487F-814B-7AE1CE114CCA--