Mailing-List: contact dev-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Received-SPF: error (athena.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Subject: Re: Problems with new maven version
From: Daniel Kulp <dkulp@apache.org>
In-Reply-To: 
 <CAK--DP8Dj_bVkfHjtNtx5cWPtVKJ37X_hgJveX4Li8AxeBNMWw@mail.gmail.com>
Date: Wed, 21 Aug 2013 08:53:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A596AF7C-D9D0-44F5-A879-9F932F52BF15@apache.org>
References: 
 <CAK--DP8Dj_bVkfHjtNtx5cWPtVKJ37X_hgJveX4Li8AxeBNMWw@mail.gmail.com>
To: dev@karaf.apache.org,
 Andreas Pieber <anpieber@gmail.com>


On Aug 21, 2013, at 8:36 AM, Andreas Pieber <anpieber@gmail.com> wrote:

> Hey guys,
>=20
> I've kind of a problem with KARAF-2395 [1]. While I've a patch making
> everything compatible to maven 3.1.x it's incompatible then to maven =
3.0.x.
> Thanks to the way we're using aether the only real option I see is to
> either set the minimum maven version to 3.1 or provide two commands; =
one
> for 3.0 and one for 3.1. Both solutions don't feel ideal for me. Any
> ideas/proposals how to progress?


I guess my suggestion would be to look at the source for the =
maven-dependency-plugin to see how it's handling some of this.   I don't =
think there is much that Karaf does that the dependency plugin  doesn't =
do something very similar to (copying artifacts, resolving tree's, =
etc..).    Since the latest dependency plugin works with both versions =
of Maven, there should be a way.

Dan


>=20
> Kind regards,
> Andreas
>=20
> [1]https://issues.apache.org/jira/browse/KARAF-2395

--=20
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com