Build ext to force a custom "http" wagon to be used...

[Jason Dillon <ja...@planet57.com>]

Is there anyway to use a build extension that provides a custom  
"org.apache.maven.wagon.Wagon" role with a "http" role-hint to be  
used instead of whatever wagon-http which Maven defaults to using?

Or is there a way to install a build extension which will result in  
the container creating a new instance of a component right away?

I'm trying to figure out how to use the current extension mechanism  
to fire up a custom proxy handler automatically and delegate all  
wagon calls to it, so that proxy component can make some educated  
decisions on where to fetch artirfacts from.  Trying to get a DSMP- 
like component that will automatically boot up *inside of maven* w/o  
any user configuration.

I tried whipping up a brain-dead wagon impl, and created a  
components.xml for it for the "http" role-hint,  
"org.apache.maven.wagon.Wagon" role and hooked it up in project/build/ 
extensions... but Maven doesn't want to use that version, it seems to  
always prefer the wagon-http from its ~/lib dir.

Is there anyway to force Maven to use a specific wagon impl for a  
role-hint?

--jason

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org