James Carpenter wrote:
Sounds like good news to me.
Can you please define "not too distant a future"? Are you talking days,
weeks, months, quarters? I realize you probably don't have an exact answer.
James, I am working hard to make it weeks, not months. Currently, there
are two pieces still WIP: repository metadata (how often to scan for
newer versions, where to store that data) and real world testing. I am
pretty sure the last one will reveal tons of things to fix, which is fun!
Will Mercury be used to entirely replace the existing
DefaultArtifactResolver mechanism?
I hope to be able to do that
What I'm really trying to ask is whether
Mercury will be a bolt on library to maven which will only be used in
special cases and which will require adapting plugins to be aware of its
existence, or if it will be the standard approach.
Standard, to be discussed and approved the community of cause
If I wait a few months
will all my problems simply disappear with maven magicially supporting what
I need?
That's the whole reason to do Mercury in the first place. But - if I
understood your question correctly - you problem will become solvable
withing standard maven, not solved. To get solved - it will require
another repository implementation, which I will happily help you to do,
but cannot do on my own as I don't know the details.
I assume you are providing concrete implementations of the necessary
interfaces to be backwards compatible with existing m2 repositories. Is
this a correct assumption?
I implemented local and remote M2 repositories for the start and will
also try to make Mercury available as ant tasks -
http://docs.codehaus.org/display/MAVEN/Mercury+1.0.0+roadmap - this I
will keep updating
Have a nice one,
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
