You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by Maczka Michal <mi...@imtf.ch> on 2005/03/11 09:17:03 UTC
RE: [jira] Created: (MNG-186) sort out fat http vs lightweight ht
tp
> -----Original Message-----
> From: Brett Porter (JIRA) [mailto:jira@codehaus.org]
> Sent: Friday, March 11, 2005 12:07 AM
> To: m2-dev@maven.apache.org
> Subject: [jira] Created: (MNG-186) sort out fat http vs
> lightweight http
>
>
> sort out fat http vs lightweight http
> -------------------------------------
>
> Key: MNG-186
> URL: http://jira.codehaus.org/browse/MNG-186
> Project: m2
> Type: Bug
> Components: maven-artifact
> Reporter: Brett Porter
>
>
> some tasks, like the use of an NTLM proxy, will require the
> use of the fat HTTP wag instead of the lightweight one -
> however, because of an identical hint it will need to be
> loaded by an alternative means.
>
>
>
Note also that "fat" http wagon can also support https protocol.
I have add getSupportedProtocols() method to wagon for handling such
situtaion when a wagon can handle more then one protcol.
This allowed to have arbitary role hints (e.g. lightwieigh-http) and
WagonManger was querying wagons to discover available protocols.
For unknown reason this method was removed.
You may also read my proposal how this can be partially fixed in a different
way (support for https must be sovled differently):
http://plexus.codehaus.org/Component+Ranking+and+Clarifed+Role+Hints
Implementationt of "component rankings" is quite trivial and this is
something which exists in other component frameworks like osgi
for handling such situations.
michal