Skip to content

Create a chameleon starter artifact #79

Description

@lordofthejars
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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions