I would like to have this optionally work across all current (and future) wagon wheels (providers).
How about the following methods? for reference -> http://maven.apache.org/wagon/wagon-provider-api/apidocs/org/apache/maven/wagon/Wagon.html Wagon.setClientProperties( Properties ); Wagon.setClientProperty( String key, String value ); That way, you can provide the data, pass it anonymously to the active wagon, and (if the wagon supports it), add those key/value pairs to any sort of client identification process in the wagon? http, http-lightweight, and webdav would obviously include http request headers. ftp, file, and ssh providers would essentially ignore the ClientProperties provided. Should we prevent, or allow, the ability to set any of the standard client properties? Such as 'USER_AGENT', or 'REFERER'? I'm leaning towards allowing it, but tossing a warning when it an overwrite situation occurs. Sound good? - Joakim Jason van Zyl wrote: > Joakime, > > Do you think you could add something that would allow us to add to set > of headers that are sent to a client, and set the client string? In > Maven I would like to accurately keep track of what versions of Maven > are actively in use and I think being able to send version information > along with the request and/or version numbers in the client string > would help us tremendously in knowing who is actually using what. > > Jason. > > --------------------------------------------------------------------- > 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]
