WARNING: This server is unstable and will be retired in the next days. If you want to keep this forum available, please request immediately a migration on the Nabble Support forum. Forums that don't receive any migration request will be deleted forever.

 « Return to Thread: [jira] (MRM-526) cache-failure policy timeout should be easily configurable

[jira] (MRM-526) cache-failure policy timeout should be easily configurable

by JIRA jira@codehaus.org :: Rate this Message:

Reply (Restricted by the Administrator) | View in Thread


    [ https://jira.codehaus.org/browse/MRM-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=295258#comment-295258 ]

Olivier Lamy commented on MRM-526:
----------------------------------

I have pasted to you the default values provided in archiva (see file http://svn.apache.org/repos/asf/archiva/branches/archiva-1.3.x/archiva-modules/archiva-base/archiva-policies/src/main/resources/META-INF/plexus/components-fragment.xml which is included in the jar archiva-policies-1.3.5.jar).
Now you can override those values as I explained to you.
For configuration values that's ehcache. See ehcache documentation.
               

> cache-failure policy timeout should be easily configurable
> ----------------------------------------------------------
>
>                 Key: MRM-526
>                 URL: https://jira.codehaus.org/browse/MRM-526
>             Project: Archiva
>          Issue Type: Improvement
>          Components: remote proxy
>    Affects Versions: 1.0-beta-2
>            Reporter: JR Boyens
>            Assignee: Olivier Lamy
>             Fix For: 1.4-M3
>
>
> set in a plexus.xml deep in archiva-policy.jar

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

 « Return to Thread: [jira] (MRM-526) cache-failure policy timeout should be easily configurable