www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Hunt (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (INFRA-4565) Migrate from legacy repo to r.a.o -- set up maven snapshot and release paths for zookeeper on nexus.
Date Thu, 22 Mar 2012 17:22:22 GMT
Migrate from legacy repo to r.a.o -- set up maven snapshot and release paths for zookeeper
on nexus.
----------------------------------------------------------------------------------------------------

                 Key: INFRA-4565
                 URL: https://issues.apache.org/jira/browse/INFRA-4565
             Project: Infrastructure
          Issue Type: Task
      Security Level: public (Regular issues)
          Components: Nexus
            Reporter: Patrick Hunt
            Assignee: Brian Demers
            Priority: Blocker


there already seems to be a zookeeper repo setup, however it's not working properly (at least
for me).

not sure if it's helps but here is our ivy file: (name=zookeeper)
http://svn.apache.org/viewvc/zookeeper/trunk/ivy.xml?view=markup

As part of this jira we want to migrate off the legacy people.apache.org publishing method
we were using, and host all of our artifacts on r.a.o

Using the details from here:
http://www.apache.org/dev/publishing-maven-artifacts.html
I copied what svn is doing and attempted to deploy our latest release, it fails with:

upload-nexus.xml:38: impossible to publish artifacts for org.apache.zookeeper#zookeeper;3.3.5:
java.io.IOException: PUT operation to URL https://repository.apache.org/service/local/staging/deploy/maven2/org.apache.zookeeper/zookeeper/zookeeper/3.3.5/zookeeper-3.3.5.jar
failed with status code 400: Bad Request

Someone on #asfinfra mentioned I may not have permissions to publish, this is odd given I'm
a pmc member and committer on the project. If someone could look into that as well it would
be great - all zk committers should be able to publish to the zk repo.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message