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 (athena.apache.org: local policy)
Message-ID: <4B8D07E3.8070109@code-sourcery.de>
Date: Tue, 02 Mar 2010 13:43:15 +0100
From: Tobias Gierke <tobias.gierke@code-sourcery.de>
User-Agent: Thunderbird 2.0.0.23 (X11/20090812)
MIME-Version: 1.0
To: Maven Developers List <dev@maven.apache.org>
Subject: Re: resolve dependencies with mercury
References: <658464.47365.qm@web59410.mail.ac4.yahoo.com>
 <0ACC1FF2-E7DE-4A1B-A2A6-CD18EEB0B23E@sonatype.com>
In-Reply-To: <0ACC1FF2-E7DE-4A1B-A2A6-CD18EEB0B23E@sonatype.com>
Content-Type: multipart/alternative;
 boundary="------------020908010504080405080701"

--------------020908010504080405080701
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hi,
> Mercury it's current form is not released, maybe not ever be integrated=
 with Maven 3.x  as it is today and may not be released. It's an experime=
nt we had hoped to be successful but hasn't made it into Maven 3.x.
>  =20
Just out of curiosity  - what exactly happened to Mercury ? To me it=20
seemed like a very good way of tackling the dependency resolution problem=
=2E
> We have started taking a different approach with Maven 3.x but it's unl=
ikely we'll have time to integrate it into 3.0.
>  =20
Is there any information on the net about how this 'different approach'=20
will look like  ? Googling 'Maven 3 dependency resolution' turns up only =

pages that talk about Mercury.

Regards,

Tobias
> Pascal, the P2 lead, now works for Sonatype so we're trying to set some=
 time aside for him to think about and try merging the models of Maven an=
d P2 together but this is not trivial and this may also never work.
>
> We've reverted to creating a composite component in Maven 3.0 called th=
e RepositorySystem. This component is working, but has not been separated=
 out into a separate library because our focus for 3.0 was complete backw=
ard compatibility at the CLI level for users. I don't know when it will b=
e separated, I don't know when/if it will be released separately and ther=
e is no documentation. So if you want to use it you'll have to surf throu=
gh the tests.
>
> We will take the Mercury builds off the grid
> On Feb 26, 2010, at 8:27 AM, Mr M=E1rton Elek wrote:
>
>  =20
>> Hi,
>>
>> I would like to use Mercury to resolve (transitive) dependencies from =
a Java SE application.
>>
>> I checked out the latest Maven 3 and Mercury source code and it works =
well except resolving transitive dependencies.
>>
>> When I try to use org.apache.maven.mercury.MavenDependencyProcessor I =
get an exception:
>>
>> java.lang.NoClassDefFoundError: org/apache/maven/model/PomClassicDomai=
nModel
>>
>> I get the same exception when I run mvn test on the mercury-it project=

>>
>> It seems that the Mercury project on the sonatype hudons is live:
>> https://grid.sonatype.org/ci/job/mercury-1.6/
>> But it doesn't seem a real maven job.
>>
>> Probably somewhere exists a newer org.apache.maven:maven-mercury artif=
act which not depends on PomClassicDomainModel but I can't find the sourc=
e of maven-mercury project.
>>
>> My questions:
>> 1. Where can I find the source of maven-mercury project?
>> 2. Is the Mercury is an active project? It seems even the maven3 trunk=
 doesn't use it?
>> 3. What is the recommended method to resolve maven dependencies from J=
ava application?
>>
>> Regards
>> mart
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
> ----------------------------------------------------------
>
>
>  =20


--------------020908010504080405080701--