You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/03/07 20:53:13 UTC
[jira] Created: (MRM-300) when a proxied repository is remove, it
re-appears when Archiva is restarted
when a proxied repository is remove, it re-appears when Archiva is restarted
----------------------------------------------------------------------------
Key: MRM-300
URL: http://jira.codehaus.org/browse/MRM-300
Project: Archiva
Issue Type: Bug
Components: design
Reporter: Brett Porter
Deleted proxied repositories reappear when Archiva is restarted.
To reproduce:
1. Log in as admin
2. Artifact Rpository -> Proxied Repositories
3. Delete the default 'central' proxied repo
4. Restart
5. Repeat steps 1-2
Result:
The previously deleted proxied repo appears in the list.
Expected Result:
The deleted repo should not appear.
Workaround:
Edit conf/archiva.xml and remove the <proxiedRepository> element.
--
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] Closed: (MRM-300) when a proxied repository is remove, it
re-appears when Archiva is restarted
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-300.
----------------------------
Resolution: Fixed
Fix Version/s: 1.0
> when a proxied repository is remove, it re-appears when Archiva is restarted
> ----------------------------------------------------------------------------
>
> Key: MRM-300
> URL: http://jira.codehaus.org/browse/MRM-300
> Project: Archiva
> Issue Type: Bug
> Components: design
> Reporter: Brett Porter
> Assigned To: Brett Porter
> Fix For: 1.0
>
>
> Deleted proxied repositories reappear when Archiva is restarted.
> To reproduce:
> 1. Log in as admin
> 2. Artifact Rpository -> Proxied Repositories
> 3. Delete the default 'central' proxied repo
> 4. Restart
> 5. Repeat steps 1-2
> Result:
> The previously deleted proxied repo appears in the list.
> Expected Result:
> The deleted repo should not appear.
> Workaround:
> Edit conf/archiva.xml and remove the <proxiedRepository> element.
--
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] Work started: (MRM-300) when a proxied repository is remove,
it re-appears when Archiva is restarted
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MRM-300 started by Brett Porter.
> when a proxied repository is remove, it re-appears when Archiva is restarted
> ----------------------------------------------------------------------------
>
> Key: MRM-300
> URL: http://jira.codehaus.org/browse/MRM-300
> Project: Archiva
> Issue Type: Bug
> Components: design
> Reporter: Brett Porter
> Assigned To: Brett Porter
>
> Deleted proxied repositories reappear when Archiva is restarted.
> To reproduce:
> 1. Log in as admin
> 2. Artifact Rpository -> Proxied Repositories
> 3. Delete the default 'central' proxied repo
> 4. Restart
> 5. Repeat steps 1-2
> Result:
> The previously deleted proxied repo appears in the list.
> Expected Result:
> The deleted repo should not appear.
> Workaround:
> Edit conf/archiva.xml and remove the <proxiedRepository> element.
--
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-300) when a proxied repository is remove, it
re-appears when Archiva is restarted
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89410 ]
Joakim Erdfelt commented on MRM-300:
------------------------------------
More accurate to say that the proxied repository is never removed from the on-disk archiva.xml
> when a proxied repository is remove, it re-appears when Archiva is restarted
> ----------------------------------------------------------------------------
>
> Key: MRM-300
> URL: http://jira.codehaus.org/browse/MRM-300
> Project: Archiva
> Issue Type: Bug
> Components: design
> Reporter: Brett Porter
> Assigned To: Brett Porter
>
> Deleted proxied repositories reappear when Archiva is restarted.
> To reproduce:
> 1. Log in as admin
> 2. Artifact Rpository -> Proxied Repositories
> 3. Delete the default 'central' proxied repo
> 4. Restart
> 5. Repeat steps 1-2
> Result:
> The previously deleted proxied repo appears in the list.
> Expected Result:
> The deleted repo should not appear.
> Workaround:
> Edit conf/archiva.xml and remove the <proxiedRepository> element.
--
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