You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/09/24 17:56:32 UTC
[jira] Created: (WAGON-315) Permament move (error 301) not handled
properly by Maven
Permament move (error 301) not handled properly by Maven
--------------------------------------------------------
Key: WAGON-315
URL: http://jira.codehaus.org/browse/WAGON-315
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http-lightweight
Affects Versions: 1.0-beta-6
Reporter: Grzegorz Slowikowski
Priority: Minor
Fix For: 1.0-beta-7
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
[jira] Commented: (MNG-4838) Permament move (error 301) not handled
properly by Maven
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236382#action_236382 ]
Brett Porter commented on MNG-4838:
-----------------------------------
requires a Wagon release to fix, see linked issue
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: MNG-4838
> URL: http://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
> Priority: Minor
> Fix For: 3.0.1
>
>
> 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
[jira] Moved: (MNG-4838) Permament move (error 301) not handled
properly by Maven
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved WAGON-315 to MNG-4838:
-----------------------------------------
Complexity: Intermediate
Fix Version/s: (was: 1.0-beta-7)
3.0.1
Component/s: (was: wagon-http-lightweight)
Artifacts and Repositories
Affects Version/s: (was: 1.0-beta-6)
2.0.11
2.2.1
3.0-beta-3
Key: MNG-4838 (was: WAGON-315)
Project: Maven 2 & 3 (was: Maven Wagon)
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: MNG-4838
> URL: http://jira.codehaus.org/browse/MNG-4838
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 3.0-beta-3, 2.2.1, 2.0.11
> Reporter: Grzegorz Slowikowski
> Priority: Minor
> Fix For: 3.0.1
>
>
> 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