The gross thing the wagon manager does for the proxy, etc is to push the settings in from the core to the wagon manager itself so there's passing it through the api.

Otherwise, I guess you'll need to pass the conflict resolver property through the artifact resolver api as well to get the details from the core into the artifact handling, and then do the lookup in the collector.

- Brett

On 28/06/2007, at 2:35 AM, Mark Hobson wrote:

On 27/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
The alternative of using role hints would be preferable, so thanks for
the pointers, I'll try implementing this now.  What's the best place
in the POM to configure the role hint with changing the schema though?
 Is there a reserved namespace of properties we could use, e.g.
maven.* so I could use maven.conflict.resolver=newest perhaps?

I'm not too clear on how you see a POM property getting through to the
DefaultArtifactCollector to obtain the default list of
ConflictResolvers.  Currently, the existing ArtifactCollector collect
method now delegates to an overloaded version that takes a list of
conflict resolvers:

ArtifactResolutionResult collect(..., List conflictResolvers )

So when delegating it needs to build a list of conflict resolvers to
use by default.  Previously this was done with a ConflictResolver
field that Plexus injected the default role-hint implementation into,
which could then be overridden from a POM extension components.xml.

Now, if we take the route of specifying the role-hint in the POM
somehow, how would this be cleanly propagated to DAC?

Cheers,

Mark

---------------------------------------------------------------------
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]

Reply via email to