[jboss-svn-commits] JBL Code SVN: r37203 - labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Fri Jul 1 11:14:11 EDT 2011
Author: tomjenkinson
Date: 2011-07-01 11:14:11 -0400 (Fri, 01 Jul 2011)
New Revision: 37203
Modified:
labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration/pom.xml
labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration/readme.txt
Log:
JBTM-854 streamlined the arquillian configuration to a single managed configuration
Modified: labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration/pom.xml
===================================================================
--- labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration/pom.xml 2011-07-01 14:50:19 UTC (rev 37202)
+++ labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration/pom.xml 2011-07-01 15:14:11 UTC (rev 37203)
@@ -22,12 +22,14 @@
</snapshots>
</repository>
</repositories>
-
+
<properties>
- <!-- Specify the JBoss AS directory to be the JBOSS_HOME environment variable -->
+ <!-- For arquillian -->
<jbossHome>${env.JBOSS_HOME}</jbossHome>
+ <!-- For the AS maven plugin -->
+ <jboss.home>${env.JBOSS_HOME}</jboss.home>
</properties>
-
+
<build>
<plugins>
<plugin>
@@ -37,129 +39,47 @@
<failOnMissingWebXml>false</failOnMissingWebXml>
</configuration>
</plugin>
+ <!-- The JBoss AS plugin deploys your war to a local JBoss AS container -->
+ <!-- To use, set the JBOSS_HOME environment variable and run: mvn package jboss-as:deploy -->
+ <plugin>
+ <groupId>org.jboss.as.plugins</groupId>
+ <artifactId>jboss-as-maven-plugin</artifactId>
+ <version>7.0.0.CR1</version>
+ </plugin>
</plugins>
</build>
<dependencies>
- <!-- Annotation processor to generate the JPA 2.0 metamodel classes for typesafe criteria queries -->
+ <!-- Include the JBoss' Java EE 6 APIs -->
+ <!-- JBoss distributes a complete set of Java EE 6 APIs including a Bill of Materials (BOM). A BOM specifies the versions of a "stack" (or a collection) of artifacts. We use this here so that we always get the correct versions of artifacts. Here we use the jboss-javaee-web-6.0 stack (you can read this as the JBoss stack of the Java EE 6 Web Profile APIs), and we use version 2.0.0.Beta1 which is the latest release of the stack. You can actually use this stack with any version of JBoss AS that implements Java EE 6, not just JBoss AS 7! -->
<dependency>
- <groupId>org.hibernate</groupId>
- <artifactId>hibernate-jpamodelgen</artifactId>
- <version>1.1.1.Final</version>
+ <groupId>org.jboss.spec</groupId>
+ <artifactId>jboss-javaee-web-6.0</artifactId>
+ <version>2.0.0.CR1</version>
+ <type>pom</type>
<scope>provided</scope>
- <!-- Excluded because it's provided by the Java EE 6 dependencies -->
- <exclusions>
- <exclusion>
- <groupId>org.hibernate.javax.persistence</groupId>
- <artifactId>hibernate-jpa-2.0-api</artifactId>
- </exclusion>
- </exclusions>
</dependency>
- <!-- Seam Solder provides convenient, portable CDI extensions such as an injectable logger -->
- <!-- Needed for running tests -->
+ <!-- We will provide some tests to check the quickstart deploys ok -->
<dependency>
- <groupId>org.jboss.seam.solder</groupId>
- <artifactId>seam-solder</artifactId>
- <version>3.0.0.Final</version>
- </dependency>
-
- <!-- JSR-303 (Bean Validation) Implementation -->
- <!-- Provides portable constraints such as @Email -->
- <!-- Hibernate Validator is shipped in JBoss AS 7 -->
- <dependency>
- <groupId>org.hibernate</groupId>
- <artifactId>hibernate-validator</artifactId>
- <version>4.1.0.Final</version>
- <scope>provided</scope>
- <exclusions>
- <exclusion>
- <groupId>org.slf4j</groupId>
- <artifactId>slf4j-api</artifactId>
- </exclusion>
- </exclusions>
- </dependency>
- <dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.8.1</version>
<scope>test</scope>
</dependency>
- <!-- Arquillian allows you to test enterprise code such as EJBs and Transactional(JTA) JPA from JUnit/TestNG -->
+ <!-- Arquillian allows you to test the example inside a container -->
<dependency>
<groupId>org.jboss.arquillian.junit</groupId>
<artifactId>arquillian-junit-container</artifactId>
<version>1.0.0.CR1</version>
<scope>test</scope>
</dependency>
-
- <!-- Include the JBoss' Java EE 6 APIs -->
- <!-- JBoss distributes a complete set of Java EE 6 APIs including a Bill of Materials (BOM). A BOM specifies the versions of a "stack" (or a collection) of artifacts. We use this here so that we always get the correct versions of artifacts. Here we use the jboss-javaee-web-6.0 stack (you can read this as the JBoss stack of the Java EE 6 Web Profile APIs), and we use version 2.0.0.Beta1 which is the latest release of the stack. You can actually use this stack with any version of JBoss AS that implements Java EE 6, not just JBoss AS 7! -->
<dependency>
- <groupId>org.jboss.spec</groupId>
- <artifactId>jboss-javaee-web-6.0</artifactId>
- <version>2.0.0.CR1</version>
- <type>pom</type>
- <scope>provided</scope>
+ <groupId>org.jboss.as</groupId>
+ <artifactId>jboss-as-arquillian-container-managed</artifactId>
+ <version>7.0.0.CR1</version>
+ <scope>test</scope>
</dependency>
</dependencies>
-
- <profiles>
- <profile>
- <!-- The default profile skips all tests, though you can tune it to run just unit tests based on a custom pattern -->
- <!-- Seperate profiles are provided for running all tests, including Arquillian tests that execute in the specified container -->
- <id>default</id>
- <activation>
- <activeByDefault>true</activeByDefault>
- </activation>
- <build>
- <plugins>
- <plugin>
- <artifactId>maven-surefire-plugin</artifactId>
- <version>2.4.3</version>
- <configuration>
- <skip>true</skip>
- </configuration>
- </plugin>
- <!-- The JBoss AS plugin deploys your war to a local JBoss AS container -->
- <!-- To use, set the JBOSS_HOME environment variable and run: mvn package jboss-as:deploy -->
- <plugin>
- <groupId>org.jboss.as.plugins</groupId>
- <artifactId>jboss-as-maven-plugin</artifactId>
- <version>7.0.0.CR1</version>
- </plugin>
- </plugins>
- </build>
- </profile>
-
- <profile>
- <!-- An optional Arquillian testing profile that executes tests in your JBoss AS instance -->
- <!-- This profile will start a new JBoss AS instance, and execute the test, shutting it down when done -->
- <!-- Run with: mvn clean test -Parq-jbossas-managed -->
- <id>arq-jbossas-managed</id>
- <dependencies>
- <dependency>
- <groupId>org.jboss.as</groupId>
- <artifactId>jboss-as-arquillian-container-managed</artifactId>
- <version>7.0.0.CR1</version>
- <scope>test</scope>
- </dependency>
- </dependencies>
- </profile>
-
- <profile>
- <!-- An optional Arquillian testing profile that executes tests in a remote JBoss AS instance -->
- <!-- Run with: mvn clean test -Parq-jbossas-remote -->
- <id>arq-jbossas-remote</id>
- <dependencies>
- <dependency>
- <groupId>org.jboss.as</groupId>
- <artifactId>jboss-as-arquillian-container-remote</artifactId>
- <version>7.0.0.CR1</version>
- <scope>test</scope>
- </dependency>
- </dependencies>
- </profile>
- </profiles>
</project>
Modified: labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration/readme.txt
===================================================================
--- labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration/readme.txt 2011-07-01 14:50:19 UTC (rev 37202)
+++ labs/jbosstm/trunk/ArjunaJTA/quickstarts/integration/readme.txt 2011-07-01 15:14:11 UTC (rev 37203)
@@ -24,6 +24,13 @@
mvn clean install -Parq-jbossas-managed
+COMMON ERROR
+------------
+If you get the following you have not exported JBOSS_HOME:
+Tests in error:
+ TestBusinessLogic: jbossHome 'null' must exist
+
+
EXPECTED OUTPUT
---------------
As well as the normal output you would expect to see from maven, you should also see:
More information about the jboss-svn-commits
mailing list