Details

    • Steps to Reproduce:
      Hide

      Use a browser to look at http://rubygems-proxy.torquebox.org/releases/rubygems/sass/maven-metadata.xml
      Verify that it has no <version> elements under the <versions>

      Show
      Use a browser to look at http://rubygems-proxy.torquebox.org/releases/rubygems/sass/maven-metadata.xml Verify that it has no <version> elements under the <versions>
    • Workaround Description:
      Hide

      Manually edit your local repository metadata files to include a version. (which is quite cumbersome and difficult to find the versions, if you don't already have some in your local repository)

      Show
      Manually edit your local repository metadata files to include a version. (which is quite cumbersome and difficult to find the versions, if you don't already have some in your local repository)

      Description

      When using the rubygems proxy maven repository,
      http://rubygems-proxy.torquebox.org/releases

      Maven fails to read the versions available from the metadata since the metadata file contain no versions.

      Look at e.g.
      http://rubygems-proxy.torquebox.org/releases/rubygems/sass/maven-metadata.xml

      This started being a problem only yesterday. I don't know what happened, since everything worked before Jan 30.

      I'm not sure if this relates to the issue TORQUE-919, but certainly seems to be the issue closets relating to this one, however the metadata doesn't fail validation (at least against the version 1 schema).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                benbrowning Ben Browning
                Reporter:
                Picadelli Stefan Grinsted
              • Votes:
                2 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: