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
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
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.
We have started taking a different approach with Maven 3.x but it's unlikely
we'll
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
ex
