You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the projects I have seen that are using Arquillian Cube, they are using standalone mode. This means that they always have to add two dependencies the core one and the cube (docker|restassured|kubernetes|openshift) ones.
Expected Behaviour
Create a project that contains both dependencies (core-standalone and cube(docker|restassured|kubernetes|openshift)) so from the UX point of view, only one jar is required.
Also, this simplifies the adoption since user don't need to understand anything about the internals of Arquillian (what does it means standalone) or use the wrong approach (they use the container mode but what they really meant is the standalone one).
Current Behaviour
Two dependencies are required.
The text was updated successfully, but these errors were encountered:
The way of doing this is by creating a maven module of type jar which will contain as dependencies the required dependencies, for example arquillian-standalone and arquillian-cube-docker.
Issue Overview
All the projects I have seen that are using Arquillian Cube, they are using standalone mode. This means that they always have to add two dependencies the core one and the cube (docker|restassured|kubernetes|openshift) ones.
Expected Behaviour
Create a project that contains both dependencies (core-standalone and cube(docker|restassured|kubernetes|openshift)) so from the UX point of view, only one jar is required.
Also, this simplifies the adoption since user don't need to understand anything about the internals of Arquillian (what does it means standalone) or use the wrong approach (they use the container mode but what they really meant is the standalone one).
Current Behaviour
Two dependencies are required.
The text was updated successfully, but these errors were encountered: