[
https://issues.apache.org/jira/browse/MRM-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15152318#comment-15152318
]
Romain Manni-Bucau commented on MRM-1911:
-----------------------------------------
Ran on tomee 7 with:
- removing hibernate-validator + validation-api jars (conflicts on 7.0.0-m1
cause bval 1.1 is shipped, removing it is a fast way to solve the issue but
deactivating as mentionned bval extension works as well)
- adding cxf management and rs service description jars in WEB-INF/lib (it is
shipped in tomee and conflicts in the webapp by classloader inheritance. Didn't
investigate much but seems cxf just does a loadClass to check it is there where
it should actually check a bit more to ensure it is usable - let me know if you
don't report it i'll do)
- adding scan.xml in WEB-INF (<scan/>) to not scan archiva webapp at all and
find @Resource etc the container can't provide (spring conflict)
Then the app starts and the GUI is "clickable" (didn't setup archiva completely
so I can't do much but it is responsive at least)
Hope it helps. Excepted the first point I think all patches I did can be added
to archiva itself. The first point can be solved providing a 1.1 bean
validation API/impl.
> Cannot start webapp
> -------------------
>
> Key: MRM-1911
> URL: https://issues.apache.org/jira/browse/MRM-1911
> Project: Archiva
> Issue Type: Bug
> Components: Web Interface
> Affects Versions: 2.2.0
> Environment: Centos 5, TomEE Plume 1.7.2, Oracle Java 1.8.0
> Reporter: Matthew Broadhead
> Attachments: archivaLog.txt
>
>
> Cannot seem to start the Archiva webapp on TomEE plume (Tomcat 7.0). I will
> upload the archiva.log stack trace
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
