[ 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: > > > 301 Moved Permanently > >

Moved Permanently

>

The document has moved here.

>
>
Apache Server at maven2-repository.dev.java.net Port 443
> > 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