The only way is to have a local build successful is to revert the versions of being-released artifacts to either the current snapshot or the latest public release. I think that can easily be done and committed to trunk. Another way is for you to download the artifacts being voted and use those (and it will be testing those ;-)
Guillaume 2014-06-30 20:53 GMT+02:00 Thomas Watson <[email protected]>: > I'm new here and this may be obvious to others. While we are in release > mode, is it expected that trunk will no longer build due to references to > the unreleased 2.0.0 parent pom? Is there a good process to follow in > order to be able to build everything locally while doing other work that is > not in the middle of being released? > > Tom > > > > [image: Inactive hide details for Guillaume Nodet ---06/30/2014 01:10:56 > PM---This is the first release of a set. It contains the paren]Guillaume > Nodet ---06/30/2014 01:10:56 PM---This is the first release of a set. It > contains the parent pom in version 2.0.0 > > From: Guillaume Nodet <[email protected]> > To: [email protected] > Date: 06/30/2014 01:10 PM > Subject: [VOTE] Release Apache Aries Parent 2.0.0 > ------------------------------ > > > > This is the first release of a set. > It contains the parent pom in version 2.0.0 > > Staging repository available at > https://repository.apache.org/content/repositories/orgapachearies-1002 > > [ ] +1 Release parent 2.0.0 > [ ] -1 Do not > > Cheers, > Guillaume Nodet > >
