suggestion/enhancement request : how to deprecate an artifact location

[Nicolas De Loof <ni...@capgemini.com>]

Hi guys,

I've got some difficulties managing our internal repository : as 
mutliple users can update it, some artifacts are deployed on multiple 
locations with != groupId. for example, java activation framework was 
deployed as jaf/jar.jar, sun/activation.jar, and is also on ibiblio as 
activation/activation.jar

It would be great for maven to include a "deprecation" mecanism for 
repository download. Adding (for example) a file 
artifactId-version.deprecated in the repo containing the alternative 
<dependency> may be a way for maven to display a warning when 
downloading dependency (or optionnaly auto-redirecting to alternative 
location).

What do you thing about this ? Can this usecase be included in maven 
next-generation repository (wagon component as far as I've understood 
maven roadmap) ?

Nico.

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.


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