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/08/09 07:27:13 UTC
[jira] Created: (MRM-462) separate configuration of managed
repositories from remote repositories
separate configuration of managed repositories from remote repositories
-----------------------------------------------------------------------
Key: MRM-462
URL: http://jira.codehaus.org/browse/MRM-462
Project: Archiva
Issue Type: Bug
Components: web application
Affects Versions: 1.0-beta-1
Reporter: Brett Porter
Priority: Critical
the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).
1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
3) I think we should consider separating them into different lists in the configuration again.
--
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-462) separate configuration of managed
repositories from remote repositories
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-462:
-----------------------------
Assignee: Brett Porter
Fix Version/s: 1.0-beta-2
> separate configuration of managed repositories from remote repositories
> -----------------------------------------------------------------------
>
> Key: MRM-462
> URL: http://jira.codehaus.org/browse/MRM-462
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.0-beta-2
>
>
> the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).
> 1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
> 2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
> 3) I think we should consider separating them into different lists in the configuration again.
--
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] Issue Comment Edited: (MRM-462) separate configuration of
managed repositories from remote repositories
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104381 ]
Brett Porter edited comment on MRM-462 at 8/9/07 12:29 AM:
-----------------------------------------------------------
some subtle issues this would address:
- https repositories get recognised as managed repositories (the path is set to ${appserver.home}/https:/...
- file URLs are overly picky and not compliant with the RFC for URLs
If this issue is not scheduled for 1.0, the above both need to be fixed independently (note that these problems appear to be in the save action itself, since if you edit the configuration by hand the information remains correct)
was:
some subtle issues this would address:
- https repositories get recognised as managed repositories (the path is set to ${appserver.home}/https:/...
- file URLs are overly picky and not compliant with the RFC for URLs
> separate configuration of managed repositories from remote repositories
> -----------------------------------------------------------------------
>
> Key: MRM-462
> URL: http://jira.codehaus.org/browse/MRM-462
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Priority: Critical
>
> the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).
> 1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
> 2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
> 3) I think we should consider separating them into different lists in the configuration again.
--
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-462) separate configuration of managed
repositories from remote repositories
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105077 ]
Brett Porter commented on MRM-462:
----------------------------------
consensus seemed to be around the original plan, but with the added condition that id's may not be duplicated between different repository types
> separate configuration of managed repositories from remote repositories
> -----------------------------------------------------------------------
>
> Key: MRM-462
> URL: http://jira.codehaus.org/browse/MRM-462
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.0-beta-2
>
>
> the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).
> 1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
> 2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
> 3) I think we should consider separating them into different lists in the configuration again.
--
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-462) separate configuration of managed
repositories from remote repositories
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-462.
----------------------------
Resolution: Fixed
merged
> separate configuration of managed repositories from remote repositories
> -----------------------------------------------------------------------
>
> Key: MRM-462
> URL: http://jira.codehaus.org/browse/MRM-462
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.0-beta-2
>
>
> the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).
> 1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
> 2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
> 3) I think we should consider separating them into different lists in the configuration again.
--
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-462) separate configuration of managed
repositories from remote repositories
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104381 ]
Brett Porter commented on MRM-462:
----------------------------------
some subtle issues this would address:
- https repositories get recognised as managed repositories (the path is set to ${appserver.home}/https:/...
- file URLs are overly picky and not compliant with the RFC for URLs
> separate configuration of managed repositories from remote repositories
> -----------------------------------------------------------------------
>
> Key: MRM-462
> URL: http://jira.codehaus.org/browse/MRM-462
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Priority: Critical
>
> the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).
> 1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
> 2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
> 3) I think we should consider separating them into different lists in the configuration again.
--
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-462) separate configuration of managed
repositories from remote repositories
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MRM-462 started by Brett Porter.
> separate configuration of managed repositories from remote repositories
> -----------------------------------------------------------------------
>
> Key: MRM-462
> URL: http://jira.codehaus.org/browse/MRM-462
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.0-beta-2
>
>
> the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).
> 1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
> 2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
> 3) I think we should consider separating them into different lists in the configuration again.
--
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-462) separate configuration of managed
repositories from remote repositories
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104876 ]
Joakim Erdfelt commented on MRM-462:
------------------------------------
Discussion on this JIRA is in progress in archiva-dev mailing list.
See http://www.nabble.com/MRM-462%3A-configuring-different-types-of-repositories-differently-tf4259505.html
> separate configuration of managed repositories from remote repositories
> -----------------------------------------------------------------------
>
> Key: MRM-462
> URL: http://jira.codehaus.org/browse/MRM-462
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.0-beta-1
> Reporter: Brett Porter
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 1.0-beta-2
>
>
> the fancy footwork to make a managed repository use all the same configuration screens as a remote repository is causing both subtle bugs (particularly in the URL handling), and a confusing user experience (settings appearing that are irrelevant to remote repositories in the edit form).
> 1) separate the forms/actions (or at least exclude the fields that are not relevant when editing the remote repos)
> 2) treat the URL (remote) as a URL and the location (managed) as a path. Don't munge anything.
> 3) I think we should consider separating them into different lists in the configuration again.
--
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