You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/08/27 23:53:51 UTC

[jira] [Created] (INFRA-6699) Released Maven artifacts 404ing in Maven Central but showing up in directory listing

Andrew Bayer created INFRA-6699:
-----------------------------------

             Summary: Released Maven artifacts 404ing in Maven Central but showing up in directory listing
                 Key: INFRA-6699
                 URL: https://issues.apache.org/jira/browse/INFRA-6699
             Project: Infrastructure
          Issue Type: Bug
          Components: Nexus
            Reporter: Andrew Bayer
            Priority: Critical


See http://central.maven.org/maven2/org/apache/jclouds/provider/rackspace-cloudservers-uk/1.6.2-incubating/ - the directory lists all the files it should (i.e., all those at https://repository.apache.org/content/repositories/releases/org/apache/jclouds/provider/rackspace-cloudservers-uk/1.6.2-incubating/) but two of the files (http://central.maven.org/maven2/org/apache/jclouds/provider/rackspace-cloudservers-uk/1.6.2-incubating/rackspace-cloudservers-uk-1.6.2-incubating.jar and http://central.maven.org/maven2/org/apache/jclouds/provider/rackspace-cloudservers-uk/1.6.2-incubating/rackspace-cloudservers-uk-1.6.2-incubating.pom) are 404ing. This is happening with other files as well (http://central.maven.org/maven2/org/apache/jclouds/jclouds-core/1.6.2-incubating/jclouds-core-1.6.2-incubating.pom, e.g.) and it's a wee bit worrying. If it's just a matter of a sync that's not done yet, cool, but I just want to be sure there isn't anything really wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira