Open Ladicek opened 6 years ago
This issue is not under our control sadly it is a requirement from docker-java
project to use Jersey. I am not sure exactly how to find a clean solution for that. Obviously we will need some kind of classpath isolation but currently I am not totally aware a possible solution for this case.
Yea I'm not asking for a solution right here right now. This specific case is a test suite where we use the Fabric8 Docker Maven plugin to run Docker containers and wanted to move to Cube. We'll keep using the Maven plugin for the time being, so it's not blocking us in any way.
Issue Overview
Cube Docker depends the
docker-java
library for talking to the Docker daemon, and that in turn depends on Jersey.However, if my test already depends on RESTEasy for various reasons (in my case, I'm starting the Keycloak Docker container and the
keycloak-admin-client
library uses RESTEasy to talk to the Keycloak server), things break.Basically, I have two implementations of JAX-RS [Client] on classpath and suffering from dependency hell.
I don't think there's a "proper" solution, but ... dare I say ... uberjar?
Expected Behaviour
Able to use RESTEasy in a test with Arquillian Cube Docker.
Current Behaviour
Not able to use RESTEasy in a test with Arquillian Cube Docker.
Steps To Reproduce
git clone https://github.com/Ladicek/cube-docker-example
mvn clean test
The commit history in that repo might be informative too.
Additional Information
The output of the commands above clearly shows that RESTEasy is used, which
docker-java
isn't prepared for: