There's also this from John:
http://docs.codehaus.org/display/MAVEN/Conflict+Resolution
It'd also be worth reviewing the "requirements" for 2.0.x to see if
anything carries over:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
How does Mercury handle the question of scope? Is that contained
within the MetadataProcessor and so delegated to maven-project?
Thanks,
Brett
On 06/08/2008, at 11:34 PM, Jason van Zyl wrote:
Here's the collector page where you might want to add your stuff:
http://docs.codehaus.org/display/MAVEN/Mercury
and here's the nitty gritty:
http://docs.codehaus.org/display/MAVEN/SAT+Based+Dependency+Resolution
And a lot of this document should be reconciled as well:
http://docs.codehaus.org/display/MAVEN/Maven+2.1+Artifact+Resolution+Specification
I think you and Oleg are most familiar with how you want this system
to be used insofar as conflict resolvers in particular and getting
those ideas aligned is important. It's also important to get the
general usage and API we present to users codified. I've asked a few
people who have used the existing implementation (Jason Dillion who
uses it in GShell, Jan who uses it in the Jetty plugin, Eugene/Igor
who use it in m2eclipse) and people who might if it was better.
Alexis who created POMStrap I've asked to look at Mercury.
I also talk about why I think Mercury is the way forward in the
future here:
http://svn.apache.org/repos/asf/maven/site/branches/maven-2.1-doco/maven-2.1-architectural-goals.apt
On 6-Aug-08, at 1:53 AM, Mark Hobson wrote:
Hi guys,
I'm happy to take a look at the new Mercury code and make sure it
supersedes my conflict resolvers patch. Any pointers to
documentation
and code would be appreciated.
Cheers,
Mark
2008/8/6 Jason van Zyl <[EMAIL PROTECTED]>:
Mark/Oleg,
Just wanted to make sure you guys were synced as Mark has written
this:
http://docs.codehaus.org/display/MAVEN/Conflict+Resolvers
And I know the plug points in Mercury provide by SAT4J deal with
most of
these but just trying to guide things into the same funnel.
On 5-Aug-08, at 4:26 PM, Jason van Zyl wrote:
Oleg,
Not sure if you've seen this, but could you take a crack at
integrating
this, if applicable, into the Mercury write up?
http://docs.codehaus.org/display/MAVEN/Maven+2.1+Artifact+Resolution+Specification
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
the course of true love never did run smooth ...
-- Shakespeare
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
We know what we are, but know not what we may be.
-- Shakespeare
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
