[ 
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

        

Reply via email to