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/07/30 07:01:13 UTC
[jira] Created: (MRM-437) admin editing of proxy connectors fails
in multiple instances
admin editing of proxy connectors fails in multiple instances
-------------------------------------------------------------
Key: MRM-437
URL: http://jira.codehaus.org/browse/MRM-437
Project: Archiva
Issue Type: Bug
Affects Versions: 1.0-beta-1
Reporter: Brett Porter
I've seen the following:
- edit first one and save (order changes)
- edit new first one and save (end up with the same connector for both, eg the blacklist is duplicated)
- in other circumstances, I'd seen editing the proxy connector produce a second one
- removing the corresponding remote repository doesn't remove the associated network proxy.
I believe this entire set of actions needs a review.
--
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-437) admin editing of proxy connectors fails
in multiple instances
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-437:
---------------------------------
Fix Version/s: (was: 1.0-beta-2)
1.0-beta-3
> admin editing of proxy connectors fails in multiple instances
> -------------------------------------------------------------
>
> Key: MRM-437
> URL: http://jira.codehaus.org/browse/MRM-437
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Fix For: 1.0-beta-3
>
>
> I've seen the following:
> - edit first one and save (order changes)
> - edit new first one and save (end up with the same connector for both, eg the blacklist is duplicated)
> - in other circumstances, I'd seen editing the proxy connector produce a second one
> - removing the corresponding remote repository doesn't remove the associated network proxy.
> I believe this entire set of actions needs a review.
--
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-437) admin editing of proxy connectors fails
in multiple instances
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt updated MRM-437:
-------------------------------
Fix Version/s: 1.0-beta-2
> admin editing of proxy connectors fails in multiple instances
> -------------------------------------------------------------
>
> Key: MRM-437
> URL: http://jira.codehaus.org/browse/MRM-437
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Fix For: 1.0-beta-2
>
>
> I've seen the following:
> - edit first one and save (order changes)
> - edit new first one and save (end up with the same connector for both, eg the blacklist is duplicated)
> - in other circumstances, I'd seen editing the proxy connector produce a second one
> - removing the corresponding remote repository doesn't remove the associated network proxy.
> I believe this entire set of actions needs a review.
--
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-437) admin editing of proxy connectors fails
in multiple instances
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-437:
-----------------------------
Assignee: (was: Brett Porter)
> admin editing of proxy connectors fails in multiple instances
> -------------------------------------------------------------
>
> Key: MRM-437
> URL: http://jira.codehaus.org/browse/MRM-437
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Fix For: 1.0-beta-2
>
>
> I've seen the following:
> - edit first one and save (order changes)
> - edit new first one and save (end up with the same connector for both, eg the blacklist is duplicated)
> - in other circumstances, I'd seen editing the proxy connector produce a second one
> - removing the corresponding remote repository doesn't remove the associated network proxy.
> I believe this entire set of actions needs a review.
--
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-437) admin editing of proxy connectors fails in
multiple instances
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt closed MRM-437.
------------------------------
Resolution: Fixed
Fixed in archiva/trunk revision 582020.
> admin editing of proxy connectors fails in multiple instances
> -------------------------------------------------------------
>
> Key: MRM-437
> URL: http://jira.codehaus.org/browse/MRM-437
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Assignee: Joakim Erdfelt
> Fix For: 1.0-beta-3
>
>
> I've seen the following:
> - edit first one and save (order changes)
> - edit new first one and save (end up with the same connector for both, eg the blacklist is duplicated)
> - in other circumstances, I'd seen editing the proxy connector produce a second one
> - removing the corresponding remote repository doesn't remove the associated network proxy.
> I believe this entire set of actions needs a review.
--
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