[
http://jira.codehaus.org/browse/MRM-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85639
]
Chris Wewerka commented on MRM-268:
-----------------------------------
Hello Nicolas, thanks for your comment.
I think there is something broken then with your described behavior in archivas
latest checkouts.
If I use an relocated artifact with our archiva, I do get the maven1 behavior
although I'm using maven 2.
E.g. I request activation/activation/1.0.2 with my maven 2.0.4 client
I do not get the pom under activation/activation with the relocation info to
javax.activation but the pom which resides under javax.activation in our
archivas cache.
Looks like a bug to me.
> 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
