On 02/12/2008, at 8:38 AM, Oleg Gusakov wrote:
It's hard to reply to a particular phrase in this thread, so I will
write a generic paragraph or two to add to Shane's comment.
Mercury was written without Maven dependencies - it exposes
DependencyProcessor interface and relies on the injecte
It's hard to reply to a particular phrase in this thread, so I will
write a generic paragraph or two to add to Shane's comment.
Mercury was written without Maven dependencies - it exposes
DependencyProcessor interface and relies on the injected implementation
to supply dependencies - being it
maven-project-builder was a refactoring and moving of certain key classes
and interfaces from maven-project, specifically for Mercury's requirement of
not being dependent on largely portions of Maven trunk. As it stands, the
maven-project-builder doesn't have any dependencies on the rest of maven
On 01/12/2008, at 4:58 AM, jallen wrote:
Should this be detected by mvn and prevented?
Yes (I'm surprised it isn't, I thought plugin dependencies were in the
reactor ordering).
So bottom line question, what is the specified behaviour for what
I'm doing?
Does maven try and do anything cl
On 01/12/2008, at 8:12 AM, Oleg Gusakov wrote:
Jason van Zyl wrote:
Oleg,
Shane and I were chatting and I think the maven-mercury module in
trunk can actually go into Mercury itself, there is nothing trunk
specific in there and almost makes you trunk free.
This kind of beats the purpose
