You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/03/19 04:49:22 UTC

[jira] Commented: (MRM-1363) Behaviour of multiple proxy connectors, persistence of configuration

    [ http://jira.codehaus.org/browse/MRM-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214433#action_214433 ] 

Brett Porter commented on MRM-1363:
-----------------------------------

Is this the default configuration, or have you customised it? The Java.NET repository is configured only to handle javax/** requests by default in its whitelist.

I'll file this in the backlog to investigate the configuration saving problems.

> 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