|
»
Created: (MEV-642) Permament move (error 301) not handled properly by Maven
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
Created: (MEV-642) Permament move (error 301) not handled properly by Maven
by JIRA jira@codehaus.org
::
Rate this Message:
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 |
|
|
Moved: (MNG-4428) Permament move (error 301) not handled properly by Maven
by JIRA jira@codehaus.org
::
Rate this Message:
[ 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 |
|
|
Updated: (MNG-4428) Permament move (error 301) not handled properly by Maven
by JIRA jira@codehaus.org
::
Rate this Message:
[ 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 |
|
|
Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven
by JIRA jira@codehaus.org
::
Rate this Message:
[ 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 |
|
|
Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven
by JIRA jira@codehaus.org
::
Rate this Message:
[ 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 |
| Free embeddable forum powered by Nabble | Forum Help |
