You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chris Wewerka (JIRA)" <ji...@codehaus.org> on 2007/01/16 15:34:40 UTC
[jira] Created: (MRM-268) Archivas relocation feature should be
configurable
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
[jira] Commented: (MRM-268) Archivas relocation feature should be
configurable
Posted by "nicolas de loof (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRM-268) Archivas relocation feature should be
configurable
Posted by "Chris Wewerka (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRM-268) Archivas relocation feature should be
configurable
Posted by "nicolas de loof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85637 ]
nicolas de loof commented on MRM-268:
-------------------------------------
Hello, I made the original contrib for the relocation feature.
Maven2 will request all POMs from archiva before requesting the artifacts, so it will handle relocations metadata itself and warn the user. Maven2 will then ask for the relocated artifact and archiva reloaction will not occur. Isn't this what you get/expect ?
Maven1 has no support for model4 POMs and will not download the POM neither read any relocation info, so it can't warn the user. The relocation from the archiva-side was designed for maven1 only, to avoid legacy/duplicated artifacts in a managed repo (my corporate repo had 5 "ejb.jar" under groupIds "ejb", "j2ee", "sun", "java.ejb" and "javax.ejb"). It should not occur when maven2 only is used.
> 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