RE: Apache Archiva 2.0.0-RC1
Hi, I cannot test ldap yet. Waiting 2.0.0 for being able to deploy archiva in the research center infrastructure. My current limited installation is showing no bug. Lots of issues are solved. I have no precise idea how but "htop" or "top" command line on the server show less amount of memory and cpu than in previous snapshot (taken 3months ago) . Happy New Year ! Eric -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : dimanche 19 janvier 2014 23:17 À : dev@archiva.apache.org Objet : Apache Archiva 2.0.0-RC1 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=Tex t&projectId=10980&Create=Create Staged repository with various redback librarires: https://archiva-repository.apache.org/archiva/repository/archiva-releases-st age 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
Re: Apache Archiva 2.0.0-RC1
On 20 January 2014 15:27, Brett Porter wrote: > 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. ? I miss your point. > > 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? I wanted to avoid too many votes :-) > > - Brett > > On 20 Jan 2014, at 9:16 am, Olivier Lamy 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 > -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Apache Archiva 2.0.0-RC1
On 21 Jan 2014, at 9:18 am, Olivier Lamy wrote: > On 20 January 2014 15:27, Brett Porter wrote: >> 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. > > ? I miss your point. If you set the ARCHIVA_BASE variable before starting to use a different conf/log directory, it ignores it (the wrapper.conf ends up with set.ARCHIVA_BASE=. instead of set.default.ARCHIVA_BASE=.). > >> >> 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? > > I wanted to avoid too many votes :-) Should be easy to pass some of the votes while RC might get re-made - I'm finding it hard to build everything right now because they depend on staged bits :) - Brett
Re: Apache Archiva 2.0.0-RC1
On 21 January 2014 11:20, Brett Porter wrote: > > On 21 Jan 2014, at 9:18 am, Olivier Lamy wrote: > >> On 20 January 2014 15:27, Brett Porter wrote: >>> 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. >> >> ? I miss your point. > > If you set the ARCHIVA_BASE variable before starting to use a different > conf/log directory, it ignores it (the wrapper.conf ends up with > set.ARCHIVA_BASE=. instead of set.default.ARCHIVA_BASE=.). Do you have time to work on that for the next RC? Or we consider this as minor? > >> >>> >>> 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? >> >> I wanted to avoid too many votes :-) > > Should be easy to pass some of the votes while RC might get re-made - I'm > finding it hard to build everything right now because they depend on staged > bits :) ok sounds good :-) > > - Brett > -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
