Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a chameleon starter artifact #79

Open
lordofthejars opened this issue Jan 18, 2018 · 0 comments
Open

Create a chameleon starter artifact #79

lordofthejars opened this issue Jan 18, 2018 · 0 comments
Assignees

Comments

@lordofthejars
Copy link
Member

Issue Overview

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.

This means that user needs to add:

<dependency>
  <groupId>org.jboss.arquillian.junit</groupId>
  <artifactId>arquillian-junit-container</artifactId>
  <scope>test</scope>
</dependency>
<dependency>
  <groupId>org.arquillian.container</groupId>
  <artifactId>arquillian-container-chameleon</artifactId>
  <version>${version.arquillian_chameleon}</version>
  <scope>test</scope>
</dependency>

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants