zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berk D. Demir" <...@mindcast.org>
Subject Re: maven-metadata in Maven Central still points to 3.3.1
Date Sat, 17 Mar 2012 21:00:14 GMT
Just wanted to ping.
Is anyone doing anything about this?

Please at least delete the RAO repo. Current situation cannot be made worse.


On Fri, Mar 9, 2012 at 11:57 AM, Berk D. Demir <bdd@mindcast.org> wrote:
> ...
> So, there are three options now.
> - The immediate solution is just to delete all the artifacts in RAO for
> now so Maven Central doesn't corrupt metadata.
> - More elegant solution is just to copy paste the Ant instructions from
> OSSRH documentation and start pushing to RAO from Ant and deleting
> people.apache.org repo (which may break Ivy2 users if they don't
> declare Maven Central in their build. ...But the odds are high they
> also rely on something else hosted in The Central)
> - The end game is to Mavenize the build process, publish to RAO and
> delete entire people.apache.org repo.
> Which ever you choose and proceed, you will make Maven, SBT, Grails
> and buildr users happy because they can reach ZK from Maven
> Central without defining additional repositories and most importantly
> all the projects which are publishing to Maven Central and depending
> on ZK can now let their users to move to newer ZK versions instead of
> being stuck with 3.3.1.
> Thanks,
> B.

View raw message