Broken remote repository confuses Archiva
-----------------------------------------
Key: MRM-1496
URL: https://jira.codehaus.org/browse/MRM-1496
Project: Archiva
Issue Type: Bug
Affects Versions: 1.3.5
Reporter: Olaf Krische
Priority: Critical
I used to have this repository in archiva:
ODF Release Repository
Identifier odf-snapshots
Name ODF Release Repository
URL http://odftoolkit.org/svn/odfdom~maven2/release/
Type Maven 2.x Repository
Since today (when i started using archiva, though) my third-party repository
looks like this for "jersey-server":
-rw-r--r-- 1 archiva archiva 291 8. Aug 15:00 jersey-server-1.8.pom
-rw-r--r-- 1 archiva archiva 63 8. Aug 15:00 jersey-server-1.8.pom.sha1
-rw-r--r-- 1 archiva archiva 55 8. Aug 15:00 jersey-server-1.8.pom.md5
-rw-r--r-- 1 archiva archiva 291 8. Aug 15:00 jersey-server-1.8.jar
-rw-r--r-- 1 archiva archiva 63 8. Aug 15:00 jersey-server-1.8.jar.sha1
-rw-r--r-- 1 archiva archiva 55 8. Aug 15:00 jersey-server-1.8.jar.md5
Both jar and pom look the same:
admin@archiva:/data/archiva/data/repositories/third-party/com/sun/jersey/jersey-server/1.8$
cat jersey-server-1.8.pom
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a
href="https://svn.odftoolkit.org/svn/odfdom~maven2/release/com/sun/jersey/jersey-server/1.8/jersey-server-1.8.pom";>here</a>.</p>
</body></html>
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
admin@archiva:/data/archiva/data/repositories/third-party/com/sun/jersey/jersey-server/1.8$
cat jersey-server-1.8.jar
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a
href="https://svn.odftoolkit.org/svn/odfdom~maven2/release/com/sun/jersey/jersey-server/1.8/jersey-server-1.8.jar";>here</a>.</p>
</body></html>
This is weird. Why Archiva even consider this?
When i call by browser:
-
http://svn.odftoolkit.org/svn/odfdom~maven2/release/com/sun/jersey/jersey-server/1.8/jersey-server-1.8.jar
I get a 302 redirect to:
-
https://svn.odftoolkit.org/svn/odfdom~maven2/release/com/sun/jersey/jersey-server/1.8/jersey-server-1.8.jar
Which then result in a proper 404.
Is it possible, that Archiva does not consider redirects or it considers a 302
with a body as a proper object?
In any way, i ended up now with lots of broken artifacts in my third-party
repository :-(
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
