maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabrice BELLINGARD (JIRA)" <j...@codehaus.org>
Subject [jira] Work started: (MRM-394) default remote repositories central, java.net are not available in remote repositories list
Date Fri, 01 Jun 2007 09:46:59 GMT

     [ http://jira.codehaus.org/browse/MRM-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Work on MRM-394 started by Fabrice BELLINGARD.

> default remote repositories central, java.net are not available in remote repositories
list
> -------------------------------------------------------------------------------------------
>
>                 Key: MRM-394
>                 URL: http://jira.codehaus.org/browse/MRM-394
>             Project: Archiva
>          Issue Type: Bug
>          Components: web application
>    Affects Versions: 1.0-alpha-1
>            Reporter: Brett Porter
>            Assignee: Fabrice BELLINGARD
>             Fix For: 1.0-alpha-1
>
>
> - without having added any configuration, add a new proxy connector
> - note that remote repositories list is empty
> Not sure if this is deliberate - is it valid to have two connectors to the same remote
repository?
> Two potential solutions:
> a) if they are allowed, repositories should be in the list
> b) if duplicates are not allowed (not sure why this would be the case), then the add
form should present an error message saying there are no available remote repositories

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

        

Mime
View raw message