[
http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=229097#action_229097
]
Graham Leggett commented on MNG-4428:
-------------------------------------
This is a major regression that completely sinks all maven versions newer than
v2.2.0, a patch has been available since March, but the patch has been ignored,
this bug is unassigned and is marked as "minor".
Is this on the radar for anyone to fix, or has it fallen through the cracks?
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: MNG-4428
> URL: http://jira.codehaus.org/browse/MNG-4428
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1
> Reporter: Grzegorz Slowikowski
> Priority: Minor
> Attachments: mng-4428.patch
>
>
> Artifact cannot be downloaded by http-lightweight-wagon used (as default) in
> all Maven versions except 2.2.0, which uses http-wagon by default.
> Instead of pom and jar files html files appear in the local repo with content
> like:
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>301 Moved Permanently</title>
> </head><body>
> <h1>Moved Permanently</h1>
> <p>The document has moved <a
> href="http://download.java.net/maven/2/org/codehaus/castor/castor-xml-schema/1.2/castor-xml-schema-1.2.pom";>here</a>.</p>
> <hr>
> <address>Apache Server at maven2-repository.dev.java.net Port 443</address>
> </body></html>
> Only Maven 2.2.0 handles 301 properly.
> By the way, I haven't expected such Apache configuration (permament move) in
> central Maven repo.
> As you can see this is not handled properly by almost all versions of Maven.
--
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
