[
http://jira.codehaus.org/browse/MRM-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof closed MRM-268.
-------------------------------
Assignee: nicolas de loof
Resolution: Won't Fix
Fix Version/s: (was: 1.1)
1.0
Relocation is only applied to maven1 request and never on POM request. It will
only occurs for maven1 that require archiva to handle it (or they will NOT get
the artifact), and will never occur for maven2 that allways request the POM
before the artifact.
> Archivas relocation feature should be configurable
> --------------------------------------------------
>
> Key: MRM-268
> URL: http://jira.codehaus.org/browse/MRM-268
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.0-alpha-1
> Reporter: Chris Wewerka
> Assignee: nicolas de loof
> Fix For: 1.0
>
>
> 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
