[jira] Commented: (MRM-547) proxy connectors: cache failures options are confusing

["Joakim Erdfelt (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MRM-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112303 ] 

Joakim Erdfelt commented on MRM-547:
------------------------------------

A discussion and decision has been made in the mailing list.
All policy settings are getting a thorough cleanup.

{noformat}
Releases (how often to check for)
  (old) IGNORED, ONCE, HOURLY, DAILY, DISABLED
  (new) ALWAYS,  ONCE, HOURLY, DAILY, NEVER
Snapshots (for often to check for)
  (old) IGNORED, ONCE, HOURLY, DAILY, DISABLED
  (new) ALWAYS,  ONCE, HOURLY, DAILY, NEVER
Cache-Failures
  (old) IGNORED, CACHED
  (new) NO,      YES
Checksum
  (old) IGNORED, FIX, FAIL
  (new) IGNORE,  FIX, FAIL
{noformat}

With new descriptions:

(for releases / snapshots policies)
* ALWAYS : Means that the artifact is always updated from the remote repo.
* ONCE : Means the artifact is updated only ever ONCE from the remote repo.  If it exists on the local repo, the remote repo is never hit for that artifact.
* HOURLY : Means the artifact is updated from the remote repo, only if it is at least one hour old on the local repo.
* DAILY : Means the artifact is updated from the remote repo, only if it is at least 1 day old on the local repo.
* NEVER : Means the artifact is never updated from the remote repo.

(for cache-failures)
* NO : Means that the existence of old failures is not checked.  All resource requests are allowed thru to the remote repo.
* YES : Means that the existence of old failures is checked, and will prevent the request from being performed against the remote repo.

(for checksum)
* IGNORE : Means the contents / validity of the checksum files is ignored.
* FIX : Means that the checksum files are regenerated from the downloaded resources.
* FAIL : Means that the checksum files are validated against the downloaded resource, if the resource does not pass the checksum validation, the resource and the checksum files are deleted from the local repository and a failure is issued for the transfer. 

> proxy connectors: cache failures options are confusing
> ------------------------------------------------------
>
>                 Key: MRM-547
>                 URL: http://jira.codehaus.org/browse/MRM-547
>             Project: Archiva
>          Issue Type: Bug
>          Components: web application
>    Affects Versions: 1.0-beta-2
>            Reporter: Brett Porter
>            Priority: Minor
>             Fix For: 1.0-beta-4
>
>
> I think this should be renamed to just "failures" which can be "cached" or "ignored", or otherwise be changed to a yes/no value for "cached failures".

-- 
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