We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Which container artifacts to use are not well documented,
They are on the read-only JBoss Community archive at container-adapters
And they do not include more recent releases of the containers.
A page within the current arquillian website documenting the container adapters.
I had to find this information by looking at the containers.yaml
I could then setup maven with the profiles:
remote
<profile> <id>arquillian-jbossas-remote</id> <dependencies> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-7.0</artifactId> <type>pom</type> <scope>provided</scope> </dependency> <dependency> <groupId>org.wildfly.arquillian</groupId> <artifactId>wildfly-arquillian-container-remote</artifactId> <version>2.0.1.Final</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.arquillian.protocol</groupId> <artifactId>arquillian-protocol-servlet</artifactId> <scope>test</scope> </dependency> </dependencies> </profile>
managed
<profile> <id>arquillian-jbossas-managed</id> <dependencies> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-7.0</artifactId> <type>pom</type> <scope>provided</scope> </dependency> <dependency> <groupId>org.wildfly.arquillian</groupId> <artifactId>wildfly-arquillian-container-managed</artifactId> <version>2.0.1.Final</version> <scope>test</scope> </dependency> <dependency> <groupId>org.jboss.arquillian.protocol</groupId> <artifactId>arquillian-protocol-servlet</artifactId> <scope>test</scope> </dependency> </dependencies> </profile> </profiles>
Then in arquillian.xml switching which one I was testing to default="true".
arquillian.xml
default="true"
<?xml version="1.0" encoding="UTF-8" ?> <arquillian xmlns="http://jboss.org/schema/arquillian" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.jboss.org/schema/arquillian http://www.jboss.org/schema/arquillian/arquillian_1_0.xsd"> <defaultProtocol type="Servlet 3.0" /> <container qualifier="jboss-eap-managed" default="false"> <configuration> <property name="jbossHome">/path/to/jboss-eap-7.3</property> <property name="serverConfig">standalone.xml</property> </configuration> </container> <container qualifier="jboss-eap-remote" default="false"> <configuration> <!-- Using default host:port --> </configuration> </container> </arquillian>
I've not yet got to the stage of using annotations to select by qualifiers.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue Overview
Which container artifacts to use are not well documented,
They are on the read-only JBoss Community archive at container-adapters
And they do not include more recent releases of the containers.
Expected Behaviour
A page within the current arquillian website documenting the container adapters.
Additional Information
I had to find this information by looking at the containers.yaml
I could then setup maven with the profiles:
remote
managed
Then in
arquillian.xml
switching which one I was testing todefault="true"
.I've not yet got to the stage of using annotations to select by qualifiers.
The text was updated successfully, but these errors were encountered: