Re: Cannot start Archiva 1.3.x
That does seem odd - did it accidentally get configured to use something like gcj when it was changed? Is there any more to the exception trace? To narrow it down, you can try these changes in wrapper.conf: - change wrapper.java.command=java to be the full path of the Java you want to use - add wrapper.debug=TRUE to the file These are if you are using the standalone install. - Brett On 15 Jul 2014, at 12:26 am, Mar4tin wrote: > Hi, > > For some obscure reason our Archiva cannot be restarted. First I thought it > was the upgrade to Java 8 that did it (something we did recently on our > server), but reverting switching back to Java 6 doesn't seem to solve this > issue. Anyone can help? > > Caused by: java.lang.IllegalStateException: Context namespace element > 'annotation-config' and its parser class > [org.springframework.context.annotation.AnnotationConfigBeanDefinitionParser] > are only available on JDK 1.5 and higher > at > org.springframework.context.config.ContextNamespaceHandler$1.parse(ContextNamespaceHandler.java:65) > at > org.springframework.beans.factory.xml.NamespaceHandlerSupport.parse(NamespaceHandlerSupport.java:69) > at > org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1297) > at > org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.parseCustomElement(BeanDefinitionParserDelegate.java:1287) > at > org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:135) > at > org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:92) > at > org.codehaus.plexus.spring.PlexusBeanDefinitionDocumentReader.registerBeanDefinitions(PlexusBeanDefinitionDocumentReader.java:85) > at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:507) > at > org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:398) > ... 43 more > > > > -- > View this message in context: > http://archiva.996284.n3.nabble.com/Cannot-start-Archiva-1-3-x-tp15686.html > Sent from the Issues mailing list archive at Nabble.com.
Re: Help understanding RepositoryContentConsumer API
On 15 Jul 2014, at 5:37 am, Matt Magoffin wrote: > If the "whenGathered" date was set to the epoch or null, or perhaps the > RepositoryScanner.FRESH_SCAN constant (with a value of 0), that would > indicate to my consumer that a "full" scan were being performed. But when > I do initiate the Directory Scan from the UI, the "whenGathered" is set to > the current time. Right - that was what I found as well (though it wasn't what I recalled). > >> We could probably add some more hooks into the overall process if you > wanted to propose such >> a change? >> >> Or is processing updates and deletions sufficient to maintain the > metadata, without having >> to start from scratch? > > If I could process updates and deletions, and know they were such, I could > maintain the metadata appropriately, yes. The reason I want to re-create > the metadata is for the case when something is deleted. I don't see how I > get informed of deletions in the RepositoryContentConsumer API, however. > Is there a way to get notified of them? In 1.3.x, there's a DatabaseCleanupConsumer that you can implement, which will get called when an artifact is deleted. In 2.0.x, there's a different event class that it'll need to be ported to. Which are you targeting? - Brett > > Cheers, > m@ >
Re: Help understanding RepositoryContentConsumer API
> In 1.3.x, there's a DatabaseCleanupConsumer that you can implement, which > will get called when an artifact is deleted. In 2.0.x, there's a different > event class that it'll need to be ported to. Which are you targeting? I see. I'm targeting 2.0.x. For reference, I posted a link to my consumer code here: http://jira.codehaus.org/browse/MRM-1427?focusedCommentId=345935 -- m@
Welcome Sascha Vogt as new committer
Hi, So welcome Sascha in the team. (We hope you will be as good as the German team :-) ). Nice to have you on board!! Cheers -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Welcome Sascha Vogt as new committer
Welcome! On 16 Jul 2014, at 11:23 am, Olivier Lamy wrote: > Hi, > > So welcome Sascha in the team. (We hope you will be as good as the > German team :-) ). > > Nice to have you on board!! > > Cheers > -- > Olivier Lamy > Ecetera: http://ecetera.com.au > http://twitter.com/olamy | http://linkedin.com/in/olamy
[VOTE] Apache Archiva 2.1.0
Hi, I'd like to release Apache Archiva 2.1.0 We fixed 22 issues ( http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10980&version=20146 ) Maven Staging repo: https://archiva-repository.apache.org/archiva/repository/archiva-releases-stage/ Distribution: https://dist.apache.org/repos/dist/dev/archiva/2.1.0/ Web site: http://archiva.apache.org/docs/2.1.0/ Vote open for 72H [+1] [0] [-1] Cheers, -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy
