Message: A new issue has been created in JIRA.
--------------------------------------------------------------------- View the issue: http://jira.codehaus.org/browse/MAVENPROXY-19 Here is an overview of the issue: --------------------------------------------------------------------- Key: MAVENPROXY-19 Summary: move cache.failures to the individual repo Type: Improvement Status: Open Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-proxy Assignee: Ben Walding Reporter: Ben Walding Created: Fri, 24 Sep 2004 8:16 PM Updated: Fri, 24 Sep 2004 8:16 PM Description: In line with mavenproxy-17, move the caching of failures option to the repository configuration. default is false. repo.<key>.cache.failures=true|false If true, failures will be cache repo.<key>.cache.hardfail=true|false If hardfail is true, unexpected errors will result in the proxy throwing an error all the way back to the client. A 404 does not constitute a hard failure, a 403 does. Pretty much anything but a 404 from an http proxy, or a file not found for a file proxy. If false, these exceptions will be swallowed (but logged), and that repository will not be included in calculations for the best artifact. --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
