You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org> on 2007/08/15 03:57:47 UTC
[jira] Created: (MRM-478) Automatic Reassign of POM embedded
repositories.
Automatic Reassign of POM embedded repositories.
------------------------------------------------
Key: MRM-478
URL: http://jira.codehaus.org/browse/MRM-478
Project: Archiva
Issue Type: New Feature
Components: remote proxy
Affects Versions: Future
Reporter: Joakim Erdfelt
Fix For: Future
This is discussed at: http://www.nabble.com/Re%3A-MRM-462%3A-configuring-different-types-of-repositories-differently-p12154720.html
Example:
1) Pull up a report of all remote repositories defined in the poms.
2) Select one of them, and a managed repository, hit 'reassign repo' button.
3) A remote repository is added to the archiva configuration.
4) A proxy connector is added between the selected managed repo and the new remote repository.
5) Then all embedded references to that remote repository now point to the managed archiva repository URL.
6) A reference is added to the auto-convert consumer that all new occurrences of this repository are converted.
--
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] Updated: (MRM-478) Automatic Reassign of POM embedded
repositories.
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt updated MRM-478:
-------------------------------
Fix Version/s: Future
Setting to a Future fix version.
> Automatic Reassign of POM embedded repositories.
> ------------------------------------------------
>
> Key: MRM-478
> URL: http://jira.codehaus.org/browse/MRM-478
> Project: Archiva
> Issue Type: New Feature
> Components: remote proxy
> Affects Versions: Future
> Reporter: Joakim Erdfelt
> Fix For: Future
>
>
> This is discussed at: http://www.nabble.com/Re%3A-MRM-462%3A-configuring-different-types-of-repositories-differently-p12154720.html
> Example:
> 1) Pull up a report of all remote repositories defined in the poms.
> 2) Select one of them, and a managed repository, hit 'reassign repo' button.
> 3) A remote repository is added to the archiva configuration.
> 4) A proxy connector is added between the selected managed repo and the new remote repository.
> 5) Then all embedded references to that remote repository now point to the managed archiva repository URL.
> 6) A reference is added to the auto-convert consumer that all new occurrences of this repository are converted.
--
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