Delays in searching proxies due to blacklist not being honoured
---------------------------------------------------------------
Key: MRM-1012
URL: http://jira.codehaus.org/browse/MRM-1012
Project: Archiva
Issue Type: Bug
Components: remote proxy
Affects Versions: 1.1.3
Environment: Windows and jdk1.5.0_16-win32
Reporter: Andrew Heald
Priority: Critical
All my proxy connectors have com/catlin/** as a blacklist item which should
mean that our own internal artifacts are not searched for through our proxy.
However, the logs show this is happening, and this is slowing down or builds
considerably. Is this an Archiva bug or a config bug on my part?
2008-11-19 11:45:53,569 [btpool0-4] INFO
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not
attempted on
http://snapshots.repository.codehaus.org//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
: NO to fetch, check-failures detected previous failure on url:
http://snapshots.repository.codehaus.org//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
2008-11-19 11:45:53,569 [btpool0-4] INFO
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not
attempted on
http://mirrors.ibiblio.org/pub/mirrors/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
: NO to fetch, check-failures detected previous failure on url:
http://mirrors.ibiblio.org/pub/mirrors/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
2008-11-19 11:45:53,569 [btpool0-4] INFO
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not
attempted on
http://junitee.sourceforge.net/repository//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
: NO to fetch, check-failures detected previous failure on url:
http://junitee.sourceforge.net/repository//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
2008-11-19 11:45:53,569 [btpool0-4] INFO
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not
attempted on
http://repo1.maven.org/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
: NO to fetch, check-failures detected previous failure on url:
http://repo1.maven.org/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
2008-11-19 11:45:53,569 [btpool0-4] INFO
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not
attempted on
http://people.apache.org/repo/m2-snapshot-repository//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
: NO to fetch, check-failures detected previous failure on url:
http://people.apache.org/repo/m2-snapshot-repository//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
2008-11-19 11:45:53,569 [btpool0-4] INFO
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not
attempted on
http://repository.jboss.com/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
: NO to fetch, check-failures detected previous failure on url:
http://repository.jboss.com/maven2//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
2008-11-19 11:45:53,569 [btpool0-4] INFO
org.apache.maven.archiva.proxy.DefaultRepositoryProxyConnectors - Transfer not
attempted on
http://gwt-maven.googlecode.com/svn/trunk/mavenrepo//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
: NO to fetch, check-failures detected previous failure on url:
http://gwt-maven.googlecode.com/svn/trunk/mavenrepo//com/catlin/scm/ProcessLaunch/1.0-SNAPSHOT/maven-metadata.xml.sha1
--
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
