[
https://jira.codehaus.org/browse/MNG-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-4838.
-----------------------------
Resolution: Duplicate
Fix Version/s: (was: 3.x / Backlog)
Assignee: Brett Porter
Yes, fixed since Maven 3.0.4 - but due to MNG-5175 rather than WAGON-314.
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: MNG-4838
> URL: https://jira.codehaus.org/browse/MNG-4838
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0.11, 2.2.1, 3.0-beta-3
> Reporter: Grzegorz Slowikowski
> Assignee: Brett Porter
> Priority: Minor
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
