Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-4838

Permament move (error 301) not handled properly by Maven

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Duplicate
    • 2.0.11, 2.2.1, 3.0-beta-3
    • None
    • None
    • Patch

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              brett Brett Porter
              gslowikowski Grzegorz Slowikowski
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: