You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eli Miller (JIRA)" <ji...@codehaus.org> on 2007/07/03 15:20:13 UTC
[jira] Created: (MRM-428) managed and remote repositories with same
name causes problems
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
[jira] Updated: (MRM-428) managed and remote repositories with same
name causes problems
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt updated MRM-428:
-------------------------------
Priority: Critical (was: Minor)
Fix Version/s: 1.0-beta-1
Issue Type: Bug (was: Improvement)
> managed and remote repositories with same name causes problems
> --------------------------------------------------------------
>
> Key: MRM-428
> URL: http://jira.codehaus.org/browse/MRM-428
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Reporter: Eli Miller
> Priority: Critical
> Fix For: 1.0-beta-1
>
>
> 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
[jira] Closed: (MRM-428) managed and remote repositories with same
name causes problems
Posted by "Joakim Erdfelt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joakim Erdfelt closed MRM-428.
------------------------------
Assignee: Joakim Erdfelt
Resolution: Fixed
Closing jira, as recent changes to the repository admin/config screens now prevents this from occuring.
> managed and remote repositories with same name causes problems
> --------------------------------------------------------------
>
> Key: MRM-428
> URL: http://jira.codehaus.org/browse/MRM-428
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Reporter: Eli Miller
> Assignee: Joakim Erdfelt
> Priority: Critical
> Fix For: 1.0-beta-3
>
>
> 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
[jira] Updated: (MRM-428) managed and remote repositories with same
name causes problems
Posted by "Maria Odea Ching (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maria Odea Ching updated MRM-428:
---------------------------------
Fix Version/s: (was: 1.0-beta-2)
1.0-beta-3
> managed and remote repositories with same name causes problems
> --------------------------------------------------------------
>
> Key: MRM-428
> URL: http://jira.codehaus.org/browse/MRM-428
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Reporter: Eli Miller
> Priority: Critical
> Fix For: 1.0-beta-3
>
>
> 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
[jira] Updated: (MRM-428) managed and remote repositories with same
name causes problems
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MRM-428:
-----------------------------
Fix Version/s: (was: 1.0-beta-1)
1.0-beta-2
scheduling for beta-2 since this is nether a feature or a blocker.
I'd like to do a more general configuration/admin review as there are plenty of other similar problems.
> managed and remote repositories with same name causes problems
> --------------------------------------------------------------
>
> Key: MRM-428
> URL: http://jira.codehaus.org/browse/MRM-428
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Reporter: Eli Miller
> Priority: Critical
> Fix For: 1.0-beta-2
>
>
> 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