Just out of curiosity - what exactly happened to Mercury ? To me it seemed
like a very good way of tackling the dependency resolution problem.
It is a good idea. This particular attempt just didn't work in time for 3.0.
But between Pascal, Benjamin and myself we'll make another attempt
On Mar 2, 2010, at 7:43 AM, Tobias Gierke wrote:
> 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 experiment we had
>> hoped to be successful but hasn't made it into Maven 3.x.
>>
> Just out of
The m2e plugin I think already does what you are looking for. It has a
dependency heirarchy and graph. I use these often to determine what
libraries are being used when there is a conflict.
---
Todd Thiessen
> -Original Message-
> From: Setter Guo [mailto:setter@yahoo.com]
> Sent:
Hi Maven users and devs,
I think a lot of guys pain on unconsistency of open-source libraries. For
example, if libA depends on libB v1, and libC depends on libB v2. If
someone(libD) want to use libA and libC at the same time, it will face problem
on upgrading libA to match libB v1. Once there a
Hi Maven users and devs,
Sorry for duplication, but yahoo mail seems very difficult to use. So I open
a gmail account, below is copy of the previous mail. If you have thoughts,
how about reply on this thread? Many Thanks!
===
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 experiment we had
hoped to be successful but hasn't made it into Maven 3.x.
Just out of curiosity - what exactly happened to Mercury ? To me it
seemed
