-
1. Re: Disabling resteasy for Arquillian Cube
l.fugaro Jul 10, 2018 9:14 AM (in response to nickarls)Hi Nik,
I'm also having trouble with it, and looking around it seems like the dependencies is hard-coded.
Take a look at the following:
Resteasy/FactoryFinder.java at master · resteasy/Resteasy · GitHub
By the way, didi you find a solution?
Thanks
Regards
Luigi
-
2. Re: Disabling resteasy for Arquillian Cube
nickarls Jul 11, 2018 1:32 AM (in response to l.fugaro)Unfortunately no, I had to drop Cube altogether and do the container startup/teardown manually in the Jenkins pipeline
-
3. Re: Disabling resteasy for Arquillian Cube
l.fugaro Jul 11, 2018 6:20 AM (in response to nickarls)I got it to work.
Don't know exactly what was the right combo-configuration, but that's what I did.
Removed the EAP 7.1 BOM and the Arquillian BOM as well.
Added all the versions manually, and for my JAX-RS application that's what I needed:
javax.enterprise cdi-api 1.2 provided org.jboss.spec.javax.annotation jboss-annotations-api_1.2_spec 1.0.0.Final provided org.jboss.spec.javax.ws.rs jboss-jaxrs-api_2.0_spec 1.0.0.Final provided org.jboss.spec.javax.ejb jboss-ejb-api_3.2_spec 1.0.0.Final provided junit junit 4.12 test org.jboss.arquillian.core arquillian-core-api 1.1.13.Final test org.jboss.arquillian.junit arquillian-junit-container 1.1.13.Final test org.arquillian.cube arquillian-cube-docker 1.15.3 test org.arquillian.cube arquillian-cube-requirement 1.15.3 test org.jboss.arquillian.protocol arquillian-protocol-servlet 1.1.13.Final test org.wildfly.arquillian wildfly-arquillian-container-managed 2.0.1.Final test org.apache.httpcomponents httpclient 4.5.3 test org.jboss.resteasy resteasy-jaxrs 3.0.24.Final test
And here is my arquillian.xml file:
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jboss.org/schema/arquillian http://jboss.org/schema/arquillian/arquillian_1_0.xsd"> STARTANDSTOP true CUBE wildfly: buildImage: dockerfileLocation: src/test/resources dockerfileName: Dockerfile.eap.71 noCache: true remove: true exposedPorts: [8080/tcp, 9990/tcp] killContainer: true await: strategy: log match: WFLYSRV0051 stdOut: true stdErr: true iterations: 100 sleepPollingTime: 1 s portBindings: [8080->8080/tcp, 9990->9990/tcp] 172.17.0.2 9990 true 8080 9990 admin admin
So, it might be a mix of few things, but I'm pretty sure with proper dependencies versions the error disappears.
IHIH,
Regards,
Luigi