1) can't change ARCHIVA_BASE variable when using the service wrapper. This is due to a change in the AppAssembler plugin that I don't agree with, but haven't had the time to revise it yet. I have a workaround we can apply in Archiva - will roll through that later this evening.
2) Next was this error: jvm 1 | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'managedRepositoryAdmin#default': Invocation of init method failed; nested exception is org.apache.archiva.admin.model.RepositoryAdminException: Cannot forcefully unlock a NativeFSLock which is held by another indexer component: /var/local/archiva/data/indexes/com.maestrodev.maestro.releases/write.lock This happened because there was a stage repository using the same indexDir. I removed the configuration from the stage directory - but do we need to force some upgrade here? 3) Need to make sure upgrade notes take care of context-root change (they may do, I haven't had a chance to check that just yet) Only got as far as starting it up, so will do more testing. Should we move forward on the redback / parent releases to get them out of the way while the overall stuff proceeds? - Brett On 20 Jan 2014, at 9:16 am, Olivier Lamy <ol...@apache.org> wrote: > Hi, > This is the RC1 of Apache Archiva 2.0.0-RC1. > If all good, 2.0.0 will be build from this one. > > Jira changes: > http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18971&styleName=Text&projectId=10980&Create=Create > > Staged repository with various redback librarires: > https://archiva-repository.apache.org/archiva/repository/archiva-releases-stage > > Apache Distribution: https://dist.apache.org/repos/dist/dev/archiva/2.0.0-RC1/ > > I will wait 3 days, if no issues found, I will start a 2.0.0 release vote > > Cheers, > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy -- Brett Porter @brettporter http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
