[
https://issues.apache.org/jira/browse/MRM-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861286#comment-16861286
]
Martin Stockhammer commented on MRM-1990:
-----------------------------------------
Hi Vojtech, what JDK (version) do you use and which payara server version? I'm
not sure, if archiva was ever tested with Payara server.
> Archiva deployment error
> ------------------------
>
> Key: MRM-1990
> URL: https://issues.apache.org/jira/browse/MRM-1990
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 2.2.3, 2.2.4
> Environment: Debian 9
> Payara 4.1.2
> Apache archiva 2.2.4
> Reporter: Vojtěch Dušátko
> Priority: Critical
> Labels: build, newbie
>
> Hello, I have a problem with deploying Archiva 2.2.\{3,4} into Payara server
> 4.1.2. It seems to be a CDI error.
> {code:java}
> remote failure: Error occurred during deployment: Exception while loading the
> app : java.lang.IllegalStateException: ContainerBase.addChild: start:
> org.apache.catalina.LifecycleException:
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'repositorySearch#maven' defined in URL
> [jar:file:/opt/payara/payara41/glassfish/domains/domain1/applications/apache-archiva-2.2.4/WEB-INF/lib/archiva-indexer-2.2.4.jar!/org/apache/archiva/indexer/search/MavenRepositorySearch.class]:
> Unsatisfied dependency expressed through constructor argument with index 0
> of type [org.apache.archiva.common.plexusbridge.PlexusSisuBridge]: : Error
> creating bean with name 'plexusSisuBridge': Invocation of init method failed;
> nested exception is java.lang.IncompatibleClassChangeError: Implementing
> class; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'plexusSisuBridge': Invocation of init method failed; nested
> exception is java.lang.IncompatibleClassChangeError: Implementing class.
> Please see server.log for more details.
> Command deploy failed.
> {code}
> Can anyone tell me where is the problem?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
