We are running Artifactory 2.2.2 using Tomcat 6.0.18, PostgreSQL 8.4, Java
6.0.18 running on a Windows 2003-R2 SP2 VM.
We also use Hudson 1.341 for our continuous builds.  We have around 10
projects which are built daily and triggered by SCM changes.

We upgraded to 2.2.2 on 4/13 and aside from a minor issue resolving the
findbugs plugin, everything has been working very well until 4/30.  Now, all
our Hudson builds fail with: "The plugin
'org.apache.maven.plugins:maven-eclipse-plugin' does not exist or no valid
version could be found".

I've looked through the artifactory.log and on 4/28 at 1:27 PM EDT it begins
to log:

[INFO ] (o.a.r.HttpRepo      :176) - repo1: Downloading
'http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml'...
[INFO ] (o.a.r.HttpRepo      :176) - repo1: Downloading
'http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml.sha1'...
[WARN ] (o.a.c.h.HttpMethodBase:2416) - Stream closed
[INFO ] (o.a.r.HttpRepo      :193) - repo1: Downloaded
'http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml.sha1'
with return code: 200.
[INFO ] (o.a.r.HttpRepo      :176) - repo1: Downloading
'http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml.md5'...
[INFO ] (o.a.r.HttpRepo      :193) - repo1: Downloaded
'http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml.md5'
with return code: 200.
[WARN ] (o.a.c.h.HttpMethodBase:2416) - Stream closed
[INFO ] (o.a.r.HttpRepo      :193) - repo1: Downloaded
'http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-eclipse-plugin/maven-metadata.xml'
with return code: 200.
[ERROR] (o.a.r.v.VirtualRepoDownloadStrategy:334) - IO exception retrieving
maven metadata content from repo 'repo1'

Prior to this time, the metadata for maven-eclipse-plugin was downloaded
without problems.

The request log, starting on 4/28 at 1:27 PM EDT, shows that every request
for maven-eclipse-plugin/maven-metadata.xml results in a 404.

I've noticed in the list there appear to be some issues regarding metadata
begining around version 2.2, these aren't checksum errors and I don't
understand why this just started happening.

Any help would be greatly appreciated.

-- 
View this message in context: 
http://forums.jfrog.org/Metadata-downloads-failing-on-2-2-2-but-not-due-to-checksum-tp4997723p4997723.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

Reply via email to