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
Usually when you use chameleon artifact, you are going to use the arquillian-container artifact as well, since you want to deploy something in the defined container you need to set as well.
But why the user needs to use both when we can have two starters (one for junit and other for testng) like we have in cube.
Expected Behaviour
Create two starters one containing the arquillian-junit-container and arquillian-container-chameleon and the other arquillian-testng-container and arquillian-container-chameleon
Current Behaviour
There is no starter artifact.
The text was updated successfully, but these errors were encountered:
Issue Overview
Usually when you use
chameleon
artifact, you are going to use thearquillian-container
artifact as well, since you want to deploy something in the defined container you need to set as well.This means that user needs to add:
But why the user needs to use both when we can have two starters (one for junit and other for testng) like we have in cube.
Expected Behaviour
Create two starters one containing the
arquillian-junit-container
andarquillian-container-chameleon
and the otherarquillian-testng-container
andarquillian-container-chameleon
Current Behaviour
There is no starter artifact.
The text was updated successfully, but these errors were encountered: