managed and remote repositories with same name causes problems
--------------------------------------------------------------
Key: MRM-428
URL: http://jira.codehaus.org/browse/MRM-428
Project: Archiva
Issue Type: Improvement
Affects Versions: 1.0-alpha-2
Reporter: Eli Miller
Priority: Minor
I created both a managed and remote repository entry with the name central --
the intent was for one to proxy the other. The administrative interfaces did
not gripe about using duplicate names but the proxy did not seem to work. In
the logs I found the following information (which looked suspect):
328579 [SocketListener0-1] DEBUG
org.apache.maven.archiva.proxy.RepositoryProxyConnectors:default - Attempting
connector: ProxyConnector[
source:ArchivaRepository[central,file:/u01/home/proj/.repos/central/]
target:ArchivaRepository[central,file:/u01/home/proj/.repos/central/]
proxyId:mpare
policy[releases]:once
policy[checksum]:fix
policy[snapshots]:disabled
policy[cache-failures]:ignored
]
When I requested that the remote central repository be deleted, the managed
repository entry was deleted instead. After I removed all central repositories
I created a managed repository named central and a remote repository named
centralExt and the proxying seemed to work as expected.
--
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
