[
http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214471#action_214471
]
Andreas Baumann edited comment on MRM-1363 at 3/20/10 7:37 AM:
---------------------------------------------------------------
Ok. Adding "rome/rome/**" to the white list of the second proxy connector does
the job.
Problem solved from my point of view.
Giving it a second thought I agree that configuring the white and black lists
is the way to go: so it's always clear what the system is doing, no implicit
assumptions.
was (Author: andreas_baumann):
Ok. Adding "rome/rome/**" to the white list the second proxy connector does
the job.
Problem solved from my point of view.
Giving it a second thought I agree that configuring the white and black lists
is the way to go: so it's always clear what the system is doing, no implicit
assumptions.
> Behaviour of multiple proxy connectors, persistence of configuration
> --------------------------------------------------------------------
>
> Key: MRM-1363
> URL: http://jira.codehaus.org/browse/MRM-1363
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: centos 5.4, 64-bit, jdk 1.6.0_16-b01
> Reporter: Andreas Baumann
> Priority: Critical
> Fix For: Backlog
>
>
> Situation, I configured two proxy connectors:
> central
> Central Repository
> http://repo1.maven.org/maven2
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: queue error
> Checksum: fix
> Snapshots: never
> followed by:
> maven2-repository.dev.java.net
> Java.net Repository for Maven 2
> http://download.java.net/maven/2/
> Return error when: always
> Cache failures: no
> Releases: always
> On remote error: stop
> Checksum: fix
> Snapshots: never
> Now I want to download the artifact 'rome/rome/1.0/jar'. The first site is
> tried (I see that in the network proxy squid), the second never (though I
> understand the 'queue error' should do that).
> Some remarks:
> - I don't see any code which actually handles the 'queue error' case
> (policies in
> the configuration parser)
> - At least the 'On remote error' setting is not persistet in the XML
> configuration
> file, because it's back to default if I restart archiva.
--
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
