maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grzegorz Slowikowski (JIRA)" <>
Subject [jira] Created: (MEV-642) Permament move (error 301) not handled properly by Maven
Date Thu, 05 Nov 2009 08:18:55 GMT
Permament move (error 301) not handled properly by Maven

                 Key: MEV-642
             Project: Maven Evangelism
          Issue Type: Bug
            Reporter: Grzegorz Slowikowski

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:

<title>301 Moved Permanently</title>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="">here</a>.</p>
<address>Apache Server at Port 443</address>

Only Maven 2.2.0 handles 301 properly.

By the way, I haven't expected such Apache configuration (permament move) in central Maven
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:
For more information on JIRA, see:


View raw message