maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <>
Subject [jira] Updated: (MRM-462) separate configuration of managed repositories from remote repositories
Date Tue, 14 Aug 2007 06:53:47 GMT


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:
>             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
> 3) I think we should consider separating them into different lists in the configuration

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message