You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Grzegorz Slowikowski (JIRA)" <ji...@codehaus.org> on 2009/11/05 09:18:55 UTC
[jira] Created: (MEV-642) Permament move (error 301) not handled
properly by Maven
Permament move (error 301) not handled properly by Maven
--------------------------------------------------------
Key: MEV-642
URL: http://jira.codehaus.org/browse/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:
<!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] Updated: (WAGON-314) Permament move (error 301) not handled
properly by Maven
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated WAGON-314:
-------------------------------
Fix Version/s: 1.0-beta-7
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> 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
>
> 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
[jira] Moved: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MEV-642 to MNG-4428:
--------------------------------------------
Version: (was: 1.2)
Complexity: Intermediate
Artifact ID: (was: castor-xml-schema)
Priority: Minor
Group ID: (was: org.codehaus.castor)
Workflow: Maven New (was: jira)
Key: MNG-4428 (was: MEV-642)
Project: Maven 2 (was: Maven Evangelism)
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: MNG-4428
> URL: http://jira.codehaus.org/browse/MNG-4428
> Project: Maven 2
> Issue Type: Bug
> Reporter: Grzegorz Slowikowski
> 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 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] Updated: (WAGON-314) Permament move (error 301) not handled
properly by Lightweight HTTP Wagon
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated WAGON-314:
----------------------------------
Fix Version/s: (was: 1.0-beta-7)
1.0-beta-8
> Permament move (error 301) not handled properly by Lightweight HTTP Wagon
> -------------------------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> 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-8
>
> 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
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Graham Leggett (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Anders Hammar (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233063#action_233063 ]
Anders Hammar commented on MNG-4428:
------------------------------------
Paul, for a workaround for Cargo, see CARGO-840. I've tried the configuration in that ticket and it does work.
> 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
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Data Nucleus (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209338#action_209338 ]
Data Nucleus commented on MNG-4428:
-----------------------------------
+1. Recent changes in SUN's M2 repo has broken local repos for me for artifacts for JMX, JMXTOOLS, JMS, MAIL.
> 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
>
> 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] Updated: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Stephen Compall (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephen Compall updated MNG-4428:
---------------------------------
Attachment: mng-4428.patch
Patch to wagon-1.0-beta-2 to drive redirects not automatically handled; see my previous comment.
> 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
[jira] Closed: (WAGON-314) Permament move (error 301) not handled
properly by Lightweight HTTP Wagon
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg closed WAGON-314.
-------------------------------
Resolution: Fixed
fixed in r1135334
> Permament move (error 301) not handled properly by Lightweight HTTP Wagon
> -------------------------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Grzegorz Slowikowski
> Assignee: Mark Struberg
> Priority: Minor
> Fix For: 2.0
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4428) Permament move (error 301)
not handled properly by Maven
Posted by "Data Nucleus (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209338#action_209338 ]
Data Nucleus edited comment on MNG-4428 at 2/6/10 9:58 AM:
-----------------------------------------------------------
+1. Recent changes in SUN's M2 repo has broken local repos for me for artifacts for JMX, JMXTOOLS, JMS, MAIL, as per one of the linked JIRAs (about log4j, saying it is log4j's POM fault, but then Maven shouldn't break the repo in the first place)
was (Author: datanucleus):
+1. Recent changes in SUN's M2 repo has broken local repos for me for artifacts for JMX, JMXTOOLS, JMS, MAIL.
> 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
>
> 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: (WAGON-314) Permament move (error 301) not
handled properly by Lightweight HTTP Wagon
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242173#action_242173 ]
Dennis Lundberg commented on WAGON-314:
---------------------------------------
I tried to apply Stephen's patch to wagon trunk, but it fails to apply. Is there any chance that you could update the patch so that it applies cleanly to trunk?
> Permament move (error 301) not handled properly by Lightweight HTTP Wagon
> -------------------------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> 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-8
>
> 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
[jira] Updated: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MNG-4428:
-----------------------------------
Component/s: Artifacts and Repositories
Affects Version/s: 2.2.1
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: MNG-4428
> URL: http://jira.codehaus.org/browse/MNG-4428
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1
> Reporter: Grzegorz Slowikowski
> 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 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-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Paul Loy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=202276#action_202276 ]
Paul Loy commented on MNG-4428:
-------------------------------
I would suggest that this is a little more important than minor. I'm having to add about 10 repos to my pom in order to work around this issue with redirects and the default maven repo.
> 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
>
> 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] Updated: (WAGON-314) Permament move (error 301) not handled
properly by Lightweight HTTP Wagon
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated WAGON-314:
-------------------------------
Summary: Permament move (error 301) not handled properly by Lightweight HTTP Wagon (was: Permament move (error 301) not handled properly by Maven)
> Permament move (error 301) not handled properly by Lightweight HTTP Wagon
> -------------------------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> 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
>
> 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
[jira] Commented: (WAGON-314) Permament move (error 301) not
handled properly by Lightweight HTTP Wagon
Posted by "Wonne Keysers (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259753#action_259753 ]
Wonne Keysers commented on WAGON-314:
-------------------------------------
I can confirm that only version 2.2.0 handles permanent redirects properly.
I would realy recommend including a fix in Maven 3 !
> Permament move (error 301) not handled properly by Lightweight HTTP Wagon
> -------------------------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> 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-8
>
> 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
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Kyle W. Cartmell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208557#action_208557 ]
Kyle W. Cartmell commented on MNG-4428:
---------------------------------------
+1 to fix ASAP - this is a huge problem as it breaks log4j 1.2.15 as Benjamin has previously stated.
> 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
>
> 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: (WAGON-314) Permament move (error 301) not handled
properly by Maven
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-4428 to WAGON-314:
-----------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Artifacts and Repositories)
wagon-http-lightweight
Affects Version/s: (was: 2.2.1)
1.0-beta-6
Key: WAGON-314 (was: MNG-4428)
Project: Maven Wagon (was: Maven 2 & 3)
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> 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
>
> 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
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Steve Kuo (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205890#action_205890 ]
Steve Kuo commented on MNG-4428:
--------------------------------
This should be major priority. Basically if any repository returns HTTP 301 Moved, then Maven blindly copies the moved HTML as a JAR. The result is that the build is broken. I've had to edit my settings.xml and create a local repository with manually downloaded JARs - a major pain. See also http://jira.codehaus.org/browse/MEV-649
> 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
>
> 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-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Stephen Compall (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212748#action_212748 ]
Stephen Compall commented on MNG-4428:
--------------------------------------
The underlying cause seems to be wagon-http-lightweight's reliance on HttpURLConnection's redirect behavior. One should first note that *all* the problematic redirects in question are cross-protocol, i.e. https->http or vice versa.
Then, consider sun.net.www.protocol.http.HttpURLConnection.followRedirect, which always returns false (don't follow) when the protocol of the old URL doesn't match that of the new one. See line 1830 in openjdk-6-src-b18-16_feb_2010 for the specifics.
Many thanks to John Raymond Wold for figuring out why the HttpURLConnection wasn't redirecting.
> 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
>
> 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] Reopened: (WAGON-314) Permament move (error 301) not handled
properly by Lightweight HTTP Wagon
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg reopened WAGON-314:
---------------------------------
> Permament move (error 301) not handled properly by Lightweight HTTP Wagon
> -------------------------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Grzegorz Slowikowski
> Assignee: Mark Struberg
> Priority: Minor
> Fix For: 2.0
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Jesse Glick (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=235562#action_235562 ]
Jesse Glick commented on MNG-4428:
----------------------------------
Confirming that the JRE's implementation does not reliably handle redirects. See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4620571 in the Evaluation section.
> 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
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "ERt (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=214778#action_214778 ]
ERt commented on MNG-4428:
--------------------------
Workaround:
1. In your local repository find pom which declare inappropriate repository
2. Remember "id" of it repository
3. Add this repository to your pom with same id and url
4. Add <enabled>false</enabled> in <releases> and <snapshots>
5. Add right repository to your pom
> 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
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Paul Davis (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=232975#action_232975 ]
Paul Davis commented on MNG-4428:
---------------------------------
ERt, I tried the workaround and it didn't work for the codehaus cargo module.
I'm with Graham on this one, what's the big deal with getting the patch applied?
> 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
[jira] Commented: (MNG-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Benjamin Jaton (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208128#action_208128 ]
Benjamin Jaton commented on MNG-4428:
-------------------------------------
Definitively a major issue since log4j 1.2.15 is impacted ( MEV-649 )
This bugs seems to be around since a long time though : MAVEN-1831 ( 31/Jan/07 ), I don't know why such a blocking issue hasn't been fixed already.
> 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
>
> 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] Closed: (WAGON-314) Permament move (error 301) not handled
properly by Lightweight HTTP Wagon
Posted by "Mark Struberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Struberg closed WAGON-314.
-------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.0-beta-8)
2.0
Assignee: Mark Struberg
redirects seem to work as expected in wagon-http-lightweight-2.0-SNAPSHOT. There are 4 TCK unit tests for the behaviour now + I tested the functionality against
http://repository.apache.org/content/repositories/snapshots/commons-daemon/commons-daemon/1.0.6-dev-SNAPSHOT
I've deployed the latest wagon-2.0-SNAPSHOT artifacts to the apache.snapshots repository.
Please test the behaviour yourself by adding something like the following snipplet to your pom:
<build>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ftp</artifactId>
<version>2.0-SNAPSHOT</version>
</extension>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-http-lightweight</artifactId>
<version>2.0-SNAPSHOT</version>
</extension>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-http</artifactId>
<version>2.0-SNAPSHOT</version>
</extension>
</extensions>
</build>
> Permament move (error 301) not handled properly by Lightweight HTTP Wagon
> -------------------------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http-lightweight
> Affects Versions: 1.0-beta-6
> Reporter: Grzegorz Slowikowski
> Assignee: Mark Struberg
> Priority: Minor
> Fix For: 2.0
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4428) Permament move (error 301)
not handled properly by Maven
Posted by "Steve Kuo (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=205890#action_205890 ]
Steve Kuo edited comment on MNG-4428 at 1/8/10 3:00 PM:
--------------------------------------------------------
This should be major priority. Basically if any repository returns HTTP 301 Moved, then Maven blindly copies the moved HTML as a JAR (an obvious bug). The result is that the build is broken. I've had to edit my settings.xml and create a local repository with manually downloaded JARs - a major pain. See also http://jira.codehaus.org/browse/MEV-649
was (Author: stevekuo):
This should be major priority. Basically if any repository returns HTTP 301 Moved, then Maven blindly copies the moved HTML as a JAR. The result is that the build is broken. I've had to edit my settings.xml and create a local repository with manually downloaded JARs - a major pain. See also http://jira.codehaus.org/browse/MEV-649
> 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
>
> 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-4428) Permament move (error 301) not handled
properly by Maven
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197320#action_197320 ]
Benjamin Bentmann commented on MNG-4428:
----------------------------------------
bq. By the way, I haven't expected such Apache configuration (permament move) in central Maven repo.
As a side note, the central Maven repository is {{repo1.maven.org}}, not "Apache Server at maven2-repository.dev.java.net Port 443".
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: MNG-4428
> URL: http://jira.codehaus.org/browse/MNG-4428
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.1
> Reporter: Grzegorz Slowikowski
> 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 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] Updated: (WAGON-314) Permament move (error 301) not handled
properly by Maven
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/WAGON-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated WAGON-314:
-------------------------------
Patch Submitted: [Yes]
> Permament move (error 301) not handled properly by Maven
> --------------------------------------------------------
>
> Key: WAGON-314
> URL: http://jira.codehaus.org/browse/WAGON-314
> 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
>
> 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