Uploaded image for project: 'Maven Ant Tasks (RETIRED)'
  1. Maven Ant Tasks (RETIRED)
  2. MANTTASKS-176

Maven Ant Tasks doesn't follow HTTP redirects

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • 2.0.8
    • None
    • dependencies task
    • None
    • Any

    Description

      Maven Ant Tasks appears to not follow HTTP redirects. Using the build.xml file at:

      http://code.google.com/p/xuml-compiler/source/browse/trunk/xUmlCompiler/build.xml

      and simply running ant (Apache Ant version 1.7.0 compiled on August 29 2007), I get

      get.maven.dependencies:
      [artifact:dependencies] Downloading: javax.mail/poms/mail-1.4.pom from java.net
      [artifact:dependencies] Transferring 0K from java.net
      [artifact:dependencies] [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = 'b521e8e2d0286806e747b071b969ba7a78dab3fb'; remote = '<!DOCTYPE' - RETRYING

      /home/sjr/.m2/repository/javax/mail/mail/1.4/mail-1.4.pom now contains

      <!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/1/javax.mail/poms/mail-1.4.pom">here</a>.</p>
      <hr>
      <address>Apache Server at maven-repository.dev.java.net Port 443</address>
      </body></html>

      rather than the expected POM files.

      This is busted.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MANTTASKS-246 mvn and dependencies ant task exclusively use <repositories> in dependency's or transient-dependency's pom.xml and does not look in maven central, stores HTTP 301 Moved Permanently html response in pom.xml

          • Major - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. WAGON-314 Permament move (error 301) not handled properly by Lightweight HTTP Wagon

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              Unassigned Unassigned
              sjr James Ring
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: