[jira] Commented: (MRM-462) separate configuration of managed repositories from remote repositories

["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