Actually, it usually takes longer for the distribution to hit the mirrors then it does to hit Maven Central.
Did you delete the previous release distribution files when you committed the new ones? We are only supposed to have a single version of each major release in the ASF dist location. Ralph On Aug 20, 2014, at 3:40 PM, Gary Gregory <[email protected]> wrote: > What we do in Commons is, as soon as the files hit Maven Central, the RM > sends the email announcement. This lets people update their builds and have > them work right away. > > Gary > > > On Wed, Aug 20, 2014 at 5:57 PM, Matt Sicker <[email protected]> wrote: > I've committed the distribution artifacts (and the site zip) to the releases > svn repo. I also released the Nexus staging repo for 2.0.2. Besides waiting a > day for the mirrors and such to propagate, I'm not sure what to do from here, > though I guess that won't be relevant until tomorrow. > > > On 20 August 2014 16:45, Matt Sicker <[email protected]> wrote: > +1 Remko Popma > +1 Gary Gregory > +1 Matt Sicker > > I'll be continuing the release now. > > -- > Matt Sicker <[email protected]> > > > > -- > Matt Sicker <[email protected]> > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory
