Community Support - Maven Central
  1. Community Support - Maven Central
  2. MVNCENTRAL-173

Zookeeper: maven-metadata.xml from people.apache.org doesn't sync to Maven Central.

    Details

    • Type: Bug Bug
    • Status: In Progress
    • Priority: Major Major
    • Resolution: Unresolved
    • Component/s: Bad Metadata
    • Labels:
      None
    • Global Rank:
      22439

      Description

      Moved from: https://issues.apache.org/jira/browse/INFRA-4414

      ZooKeeper uses people.apache.org repo to publish their Maven artifacts and this directory gets synced to Maven Central.

      The problem is, maven-metadata.xml which is used to find out the latest release version doesn't get synced to Maven Central but other artifacts do.

      Here's the up-to-date metadata from people.apache.org
      http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/zookeeper/zookeeper/maven-metadata.xml
      Gives version 3.4.2 as the current version. Released Dec 29, 2011.

      Here's the what is in Maven Central.
      http://repo1.maven.org/maven2/org/apache/zookeeper/zookeeper/maven-metadata.xml
      Gives version 3.3.1 as the current version; released Aug 9, 2010.

      Because of this problem, projects declaring ZooKeeper as a dependency and publishing their artifacts on Maven Central cannot pull the latest version but can only find 3.3.1 although the artifacts of the newer versions make it to Maven Central.

      This was discussed in ZK mailing list on Dec, 2011.
      http://mail-archives.apache.org/mod_mbox/zookeeper-user/201112.mbox/browser

        Activity

        Hide
        Juven Xu added a comment -

        same group are being synced from RAO as well: https://repository.apache.org/content/repositories/releases/org/apache/zookeeper/zookeeper/

        so metadata will never be correct unless we remove one of the sources

        Show
        Juven Xu added a comment - same group are being synced from RAO as well: https://repository.apache.org/content/repositories/releases/org/apache/zookeeper/zookeeper/ so metadata will never be correct unless we remove one of the sources
        Hide
        Brian Demers added a comment -

        Thanks juven, I missed that one.
        I thought I had checked that first, but I guess I only searched through the ASF INFRA issues to see if it had been added.

        I'll take care of this.

        Show
        Brian Demers added a comment - Thanks juven, I missed that one. I thought I had checked that first, but I guess I only searched through the ASF INFRA issues to see if it had been added. I'll take care of this.
        Hide
        Juven Xu added a comment -

        cool, thanks

        Show
        Juven Xu added a comment - cool, thanks
        Hide
        Berk D. Demir added a comment -

        Hey Brian,

        Any updates on this issue?

        Show
        Berk D. Demir added a comment - Hey Brian, Any updates on this issue?
        Hide
        Brian Demers added a comment -

        Its been on my TODO list. I get to this right now

        Show
        Brian Demers added a comment - Its been on my TODO list. I get to this right now
        Hide
        Brian Fox added a comment -

        Berk, the syncs can only come from one location or the metadata will be broken. The old rsyncs are being phased out so you should continue to use Nexus. We can redo the migration on the server side and repair the metadata. Do you need help with your build to make the adjustment?

        Show
        Brian Fox added a comment - Berk, the syncs can only come from one location or the metadata will be broken. The old rsyncs are being phased out so you should continue to use Nexus. We can redo the migration on the server side and repair the metadata. Do you need help with your build to make the adjustment?
        Hide
        Berk D. Demir added a comment -

        Brian (Fox),

        I'm not a ZooKeeper developer but a developer whose projects are in Maven Central and have ZK dependencies.

        I wrote this to ZK list in the past and they seem to be using rsync method currently. I will write to ZK list and point this discussion; ask how possible it is to change their release cycle and offer help to moving to Nexus and Mavenizing ZK.

        This is how ZooKeeper project makes the releases currently. https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease (Ant, md5sum and manual scp copies to people.apache.org)

        Show
        Berk D. Demir added a comment - Brian (Fox), I'm not a ZooKeeper developer but a developer whose projects are in Maven Central and have ZK dependencies. I wrote this to ZK list in the past and they seem to be using rsync method currently. I will write to ZK list and point this discussion; ask how possible it is to change their release cycle and offer help to moving to Nexus and Mavenizing ZK. This is how ZooKeeper project makes the releases currently. https://cwiki.apache.org/confluence/display/ZOOKEEPER/HowToRelease (Ant, md5sum and manual scp copies to people.apache.org)
        Hide
        Brian Fox added a comment -

        The issues is that zookeeper needs to use repository.apache.org to do the releases. They moved from people.apache.org sometime in the past and now this is the only place central will pickup releases from. There's no way to go back, in fact infra intends to deprecate people.a.o's repo in the near future.

        Show
        Brian Fox added a comment - The issues is that zookeeper needs to use repository.apache.org to do the releases. They moved from people.apache.org sometime in the past and now this is the only place central will pickup releases from. There's no way to go back, in fact infra intends to deprecate people.a.o's repo in the near future.
        Hide
        Berk D. Demir added a comment -

        If we go back to real problem, metadata is corrupted because there are (were?) two sync sources towards Central.

        In the past ZK developers made a release to RAO (3.3.1) but that was all and kept pushing newer releases to people.a.o

        Again, I'm NOT a ZooKeeper developer so I'm no position to make the decision to switch to using Apache's Nexus. I've sent numerous mails to about this issue and provided the ZK developers with necessary step-by-step documentation on how to make releases to Nexus with Ant.

        Patrick Hunt of ZooKeeper created INFRA-4450 https://issues.apache.org/jira/browse/INFRA-4550 asking to remove this repository so Central can pickup the maven-metadata.xml from people.a.o and not overwrite it with the one from RAO. If currently the sync is only from RAO to Central and people.a.o is completely removed, this won't solve the problem as well.

        ZooKeeper is making releases but the most recent one in Central is 3.3.1 (now 15 months old). Any other project depending on ZK and hosting artifacts on Central cannot declare a dependency to newer versions of ZK because one cannot include repositories in their POM when publishing to Central.

        Show
        Berk D. Demir added a comment - If we go back to real problem, metadata is corrupted because there are (were?) two sync sources towards Central. In the past ZK developers made a release to RAO (3.3.1) but that was all and kept pushing newer releases to people.a.o Again, I'm NOT a ZooKeeper developer so I'm no position to make the decision to switch to using Apache's Nexus. I've sent numerous mails to about this issue and provided the ZK developers with necessary step-by-step documentation on how to make releases to Nexus with Ant. Patrick Hunt of ZooKeeper created INFRA-4450 https://issues.apache.org/jira/browse/INFRA-4550 asking to remove this repository so Central can pickup the maven-metadata.xml from people.a.o and not overwrite it with the one from RAO. If currently the sync is only from RAO to Central and people.a.o is completely removed, this won't solve the problem as well. ZooKeeper is making releases but the most recent one in Central is 3.3.1 (now 15 months old). Any other project depending on ZK and hosting artifacts on Central cannot declare a dependency to newer versions of ZK because one cannot include repositories in their POM when publishing to Central.

          People

          • Assignee:
            Brian Demers
            Reporter:
            Brian Demers
            Last Updated By:
            Berk D. Demir
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Date of First Response: