Infrastructure
  1. Infrastructure
  2. INFRA-4550

remove zookeeper mvn artifacts from repo.apache.org

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Fix Version/s: Initial Clearing
    • Component/s: Nexus
    • Labels:
      None

      Description

      A maven user has reported an issue with zookeeper mvn artifacts on repo.apache.org causing corruption on Maven Central. Based on the information provided to us he's saying that removing these artifacts from repo.apache.org will resolve the problem (and not cause any other side effects), see here:

      http://markmail.org/message/mokbfqxpzjxtgxhe

      No one on our team remembers setting up RAO, would it be possible for you to do this? This is RAO only, we plan to continue to put artifacts onto people.apache.org until we move over to nexus.

        Issue Links

          Activity

          Patrick Hunt created issue -
          Hide
          Gavin added a comment -
          re-assign and add component
          Show
          Gavin added a comment - re-assign and add component
          Gavin made changes -
          Field Original Value New Value
          Assignee Brian Demers [ bdemers ]
          Component/s Nexus [ 12312660 ]
          Brian Demers made changes -
          Assignee Brian Demers [ bdemers ] Brian Fox [ brianf ]
          Brian Demers made changes -
          Link This issue is related to INFRA-4558 [ INFRA-4558 ]
          Hide
          Brian Fox added a comment -
          The new zookeeper releases need to be published to repository.apache.org as this is where central is expecting to find them. This is why the folder on people.apache.org's old repo is not writable, to prevent accidental releases. If you need help publishing to repository.a.o, then we can help sort that out.
          Show
          Brian Fox added a comment - The new zookeeper releases need to be published to repository.apache.org as this is where central is expecting to find them. This is why the folder on people.apache.org's old repo is not writable, to prevent accidental releases. If you need help publishing to repository.a.o, then we can help sort that out.
          Hide
          Patrick Hunt added a comment -
          Hi, thanks for the help. Please assume that i know nothing about the intricacies of publishing maven artifacts. (because I don't) Also for the moment we are not using nexus.

          Could you please comment on how the "maven" section at the following link should be updated to fit the requirements/restrictions just stated in the previous comment?
          https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease

          Thanks much!
          Show
          Patrick Hunt added a comment - Hi, thanks for the help. Please assume that i know nothing about the intricacies of publishing maven artifacts. (because I don't) Also for the moment we are not using nexus. Could you please comment on how the "maven" section at the following link should be updated to fit the requirements/restrictions just stated in the previous comment? https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease Thanks much!
          Hide
          Patrick Hunt added a comment -
          I just got Joe's email from infra about the move off of people.apache.org. Given these infra changes, should we consider moving to nexus? Is there any real difference btw moving to nexus vs moving to repository.apache.org?
          Show
          Patrick Hunt added a comment - I just got Joe's email from infra about the move off of people.apache.org. Given these infra changes, should we consider moving to nexus? Is there any real difference btw moving to nexus vs moving to repository.apache.org?
          Hide
          Gavin added a comment -
          Show
          Gavin added a comment - https://repository.apache.org/ is nexus
          Hide
          Patrick Hunt added a comment -
          lol. That's what I was saying before ("assume that i know nothing about the intricacies of publishing maven artifacts").

          Thanks Gavin!
          Show
          Patrick Hunt added a comment - lol. That's what I was saying before ("assume that i know nothing about the intricacies of publishing maven artifacts"). Thanks Gavin!
          Hide
          Gavin added a comment -
          no problerm :)
          Show
          Gavin added a comment - no problerm :)
          Hide
          Patrick Hunt added a comment -
          Brian please hold off on making this change while I re-evaluate the options based on the email Joe just sent out today. Thanks.
          Show
          Patrick Hunt added a comment - Brian please hold off on making this change while I re-evaluate the options based on the email Joe just sent out today. Thanks.
          Hide
          Patrick Hunt added a comment -
          Based on the data from here:
          http://www.apache.org/dev/publishing-maven-artifacts.html

          I updated our ivy/ant build system to publish artifacts to the repo, when I run it I see the following:

          bq. impossible to publish artifacts for org.apache.zookeeper#zookeeper;3.3.5: java.io.IOException: Access to URL https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/zookeeper/zookeeper/3.3.5/zookeeper-3.3.5.jar was refused by the server: Unauthorized

          when I look at https://repository.apache.org I see zookeeper listed, however it seems I'm unauthorized to actually publish. Please authorize me - likely the entire zk commiter list should be so authorized.
          Show
          Patrick Hunt added a comment - Based on the data from here: http://www.apache.org/dev/publishing-maven-artifacts.html I updated our ivy/ant build system to publish artifacts to the repo, when I run it I see the following: bq. impossible to publish artifacts for org.apache.zookeeper#zookeeper;3.3.5: java.io.IOException: Access to URL https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/zookeeper/zookeeper/3.3.5/zookeeper-3.3.5.jar was refused by the server: Unauthorized when I look at https://repository.apache.org I see zookeeper listed, however it seems I'm unauthorized to actually publish. Please authorize me - likely the entire zk commiter list should be so authorized.
          Hide
          Patrick Hunt added a comment -
          Closing this issue and will open a new one to support migrating from legacy method to r.a.o.
          Show
          Patrick Hunt added a comment - Closing this issue and will open a new one to support migrating from legacy method to r.a.o.
          Patrick Hunt made changes -
          Status Open [ 1 ] Closed [ 6 ]
          Resolution Invalid [ 6 ]
          Tony Stevenson made changes -
          Workflow jira [ 12658458 ] INFRA Workflow [ 12711440 ]
          Gavin made changes -
          Fix Version/s Initial Clearing [ 12325964 ]

            People

            • Assignee:
              Brian Fox
              Reporter:
              Patrick Hunt
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development