[ http://jira.codehaus.org/browse/MRM-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87572 ]
nicolas de loof commented on MRM-268: ------------------------------------- The latest archiva build doesn't handle relocation from the DAV api. I've reopend MRM-153 and will investigate this one when solved. > Archivas relocation feature should be configurable > -------------------------------------------------- > > Key: MRM-268 > URL: http://jira.codehaus.org/browse/MRM-268 > Project: Archiva > Issue Type: Improvement > Reporter: Chris Wewerka > > Archiva automatically delivers the new pom and jar for a relocated artifact > to a maven client. > The downside of this feature is that clients do not get a warning that the > artifact is relocated anymore. > In a "All-Maven2" environment this warning is quite good, and gives the > developer a hint and a motivation (get rid of the warning ;-) ) to use the > new groupId. > So I think it would be a good idea to make this feature configurable, so the > archiva admin can turn it off. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira