Berk D. Demir 2011-12-09, 22:44
Mahadev Konar 2011-12-11, 02:08
Berk D. Demir 2011-12-12, 10:44
Patrick Hunt 2011-12-12, 17:03
Berk D. Demir 2011-12-12, 21:37
Patrick Hunt 2011-12-12, 22:04
Patrick Hunt 2011-12-12, 22:55
Berk D. Demir 2012-03-06, 18:24
Patrick Hunt 2012-03-09, 18:12
Berk D. Demir 2012-03-09, 19:57
Berk D. Demir 2012-03-17, 21:00
-Re: maven-metadata in Maven Central still points to 3.3.1
Patrick Hunt 2012-03-18, 05:14
On Sat, Mar 17, 2012 at 2:00 PM, Berk D. Demir <[EMAIL PROTECTED]> wrote:
> Just wanted to ping.
> Is anyone doing anything about this?
> Please at least delete the RAO repo. Current situation cannot be made worse.
here's the request with infra:
> On Fri, Mar 9, 2012 at 11:57 AM, Berk D. Demir <[EMAIL PROTECTED]> 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.
Berk D. Demir 2012-03-18, 06:47