torsten@1: <?xml version="1.0" encoding="UTF-8"?>
torsten@1: <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
torsten@1:     xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
torsten@1:     <modelVersion>4.0.0</modelVersion>
torsten@1: 
torsten@1:     <groupId>de.intevation</groupId>
torsten@1:     <artifactId>lada</artifactId>
torsten@1:     <version>1.0-SNAPSHOT</version>
torsten@1:     <packaging>war</packaging>
torsten@1:     <name>Java EE 6 webapp project</name>
torsten@1:     <description>A starter Java EE 6 webapp project for use on JBoss AS 7.1 / EAP 6, generated from the jboss-javaee6-webapp archetype</description>
torsten@1: 
torsten@1:     <properties>
torsten@1:         <!-- Explicitly declaring the source encoding eliminates the following 
torsten@1:             message: -->
torsten@1:         <!-- [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
torsten@1:             resources, i.e. build is platform dependent! -->
torsten@1:         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
torsten@1:         <!-- Define the version of JBoss' Java EE 6 APIs and Tools we want 
torsten@1:             to import. -->
torsten@1:         <jboss.bom.version>1.0.0.Final</jboss.bom.version>
torsten@1:         <!-- Alternatively, comment out the above line, and un-comment the 
torsten@1:             line below to use version 1.0.0.M12-redhat-1 which is a release certified 
torsten@1:             to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6 
torsten@1:             maven repository. -->
torsten@1:         <!-- <jboss.bom.version>1.0.0.M12-redhat-1</jboss.bom.version>> -->
torsten@1:     </properties>
torsten@1: 
torsten@1: 
torsten@1:     <dependencyManagement>
torsten@1:         <dependencies>
torsten@1:             <!-- JBoss distributes a complete set of Java EE 6 APIs including 
torsten@1:                 a Bill of Materials (BOM). A BOM specifies the versions of a "stack" (or 
torsten@1:                 a collection) of artifacts. We use this here so that we always get the correct 
torsten@1:                 versions of artifacts. Here we use the jboss-javaee-6.0-with-tools stack 
torsten@1:                 (you can read this as the JBoss stack of the Java EE 6 APIs, with some extras 
torsten@1:                 tools for your project, such as Arquillian for testing) and the jboss-javaee-6.0-with-hibernate 
torsten@1:                 stack you can read this as the JBoss stack of the Java EE 6 APIs, with extras 
torsten@1:                 from the Hibernate family of projects) -->
torsten@1:             <dependency>
torsten@1:                 <groupId>org.jboss.bom</groupId>
torsten@1:                 <artifactId>jboss-javaee-6.0-with-tools</artifactId>
torsten@1:                 <version>${jboss.bom.version}</version>
torsten@1:                 <type>pom</type>
torsten@1:                 <scope>import</scope>
torsten@1:             </dependency>
torsten@1:             <dependency>
torsten@1:                 <groupId>org.jboss.bom</groupId>
torsten@1:                 <artifactId>jboss-javaee-6.0-with-hibernate</artifactId>
torsten@1:                 <version>${jboss.bom.version}</version>
torsten@1:                 <type>pom</type>
torsten@1:                 <scope>import</scope>
torsten@1:             </dependency>
torsten@1:         </dependencies>
torsten@1:     </dependencyManagement>
torsten@1:     
torsten@1:     <dependencies>
torsten@1: 
torsten@1:         <!-- First declare the APIs we depend on and need for compilation. 
torsten@1:             All of them are provided by JBoss AS 7 -->
torsten@1: 
torsten@1:         <!-- Import the CDI API, we use provided scope as the API is included 
torsten@1:             in JBoss AS 7 -->
torsten@1:         <dependency>
torsten@1:             <groupId>javax.enterprise</groupId>
torsten@1:             <artifactId>cdi-api</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Import the Common Annotations API (JSR-250), we use provided 
torsten@1:             scope as the API is included in JBoss AS 7 -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.jboss.spec.javax.annotation</groupId>
torsten@1:             <artifactId>jboss-annotations-api_1.1_spec</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Import the JAX-RS API, we use provided scope as the API is included 
torsten@1:             in JBoss AS 7 -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.jboss.spec.javax.ws.rs</groupId>
torsten@1:             <artifactId>jboss-jaxrs-api_1.1_spec</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Import the JPA API, we use provided scope as the API is included 
torsten@1:             in JBoss AS 7 -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.hibernate.javax.persistence</groupId>
torsten@1:             <artifactId>hibernate-jpa-2.0-api</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Import the EJB API, we use provided scope as the API is included 
torsten@1:             in JBoss AS 7 -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.jboss.spec.javax.ejb</groupId>
torsten@1:             <artifactId>jboss-ejb-api_3.1_spec</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- JSR-303 (Bean Validation) Implementation -->
torsten@1:         <!-- Provides portable constraints such as @Email -->
torsten@1:         <!-- Hibernate Validator is shipped in JBoss AS 7 -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.hibernate</groupId>
torsten@1:             <artifactId>hibernate-validator</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:             <exclusions>
torsten@1:                 <exclusion>
torsten@1:                     <groupId>org.slf4j</groupId>
torsten@1:                     <artifactId>slf4j-api</artifactId>
torsten@1:                 </exclusion>
torsten@1:             </exclusions>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Import the JSF API, we use provided scope as the API is included 
torsten@1:             in JBoss AS 7 -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.jboss.spec.javax.faces</groupId>
torsten@1:             <artifactId>jboss-jsf-api_2.1_spec</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Now we declare any tools needed -->
torsten@1: 
torsten@1:         <!-- Annotation processor to generate the JPA 2.0 metamodel classes 
torsten@1:             for typesafe criteria queries -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.hibernate</groupId>
torsten@1:             <artifactId>hibernate-jpamodelgen</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Annotation processor that raising compilation errors whenever 
torsten@1:             constraint annotations are incorrectly used. -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.hibernate</groupId>
torsten@1:             <artifactId>hibernate-validator-annotation-processor</artifactId>
torsten@1:             <scope>provided</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Needed for running tests (you may also use TestNG) -->
torsten@1:         <dependency>
torsten@1:             <groupId>junit</groupId>
torsten@1:             <artifactId>junit</artifactId>
torsten@1:             <scope>test</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <!-- Optional, but highly recommended -->
torsten@1:         <!-- Arquillian allows you to test enterprise code such as EJBs and 
torsten@1:             Transactional(JTA) JPA from JUnit/TestNG -->
torsten@1:         <dependency>
torsten@1:             <groupId>org.jboss.arquillian.junit</groupId>
torsten@1:             <artifactId>arquillian-junit-container</artifactId>
torsten@1:             <scope>test</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:         <dependency>
torsten@1:             <groupId>org.jboss.arquillian.protocol</groupId>
torsten@1:             <artifactId>arquillian-protocol-servlet</artifactId>
torsten@1:             <scope>test</scope>
torsten@1:         </dependency>
torsten@1: 
torsten@1:     </dependencies>
torsten@1: 
torsten@1:     <build>
torsten@1:         <!-- Maven will append the version to the finalName (which is the 
torsten@1:             name given to the generated war, and hence the context root) -->
torsten@1:         <finalName>${project.artifactId}</finalName>
torsten@1:         <plugins>
torsten@1:             <!-- Compiler plugin enforces Java 1.6 compatibility and activates 
torsten@1:                 annotation processors -->
torsten@1:             <plugin>
torsten@1:                 <artifactId>maven-compiler-plugin</artifactId>
torsten@1:                 <version>2.3.1</version>
torsten@1:                 <configuration>
torsten@1:                     <source>1.6</source>
torsten@1:                     <target>1.6</target>
torsten@1:                 </configuration>
torsten@1:             </plugin>
torsten@1:             <plugin>
torsten@1:                 <artifactId>maven-war-plugin</artifactId>
torsten@1:                 <version>2.1.1</version>
torsten@1:                 <configuration>
torsten@1:                     <!-- Java EE 6 doesn't require web.xml, Maven needs to 
torsten@1:                         catch up! -->
torsten@1:                     <failOnMissingWebXml>false</failOnMissingWebXml>
torsten@1:                 </configuration>
torsten@1:             </plugin>
torsten@1:             <!-- The JBoss AS plugin deploys your war to a local JBoss AS 
torsten@1:                 container -->
torsten@1:             <!-- To use, run: mvn package jboss-as:deploy -->
torsten@1:             <plugin>
torsten@1:                 <groupId>org.jboss.as.plugins</groupId>
torsten@1:                 <artifactId>jboss-as-maven-plugin</artifactId>
torsten@1:                 <version>7.1.1.Final</version>
torsten@1:             </plugin>
torsten@1:         </plugins>
torsten@1:     </build>
torsten@1: 
torsten@1:     <profiles>
torsten@1:         <profile>
torsten@1:             <!-- The default profile skips all tests, though you can tune 
torsten@1:                 it to run just unit tests based on a custom pattern -->
torsten@1:             <!-- Seperate profiles are provided for running all tests, including 
torsten@1:                 Arquillian tests that execute in the specified container -->
torsten@1:             <id>default</id>
torsten@1:             <activation>
torsten@1:                 <activeByDefault>true</activeByDefault>
torsten@1:             </activation>
torsten@1:             <build>
torsten@1:                 <plugins>
torsten@1:                     <plugin>
torsten@1:                         <artifactId>maven-surefire-plugin</artifactId>
torsten@1:                         <version>2.4.3</version>
torsten@1:                         <configuration>
torsten@1:                             <skip>true</skip>
torsten@1:                         </configuration>
torsten@1:                     </plugin>
torsten@1:                 </plugins>
torsten@1:             </build>
torsten@1:         </profile>
torsten@1: 
torsten@1:         <profile>
torsten@1:             <!-- An optional Arquillian testing profile that executes tests 
torsten@1:                 in your JBoss AS instance -->
torsten@1:             <!-- This profile will start a new JBoss AS instance, and execute 
torsten@1:                 the test, shutting it down when done -->
torsten@1:             <!-- Run with: mvn clean test -Parq-jbossas-managed -->
torsten@1:             <id>arq-jbossas-managed</id>
torsten@1:             <dependencies>
torsten@1:                 <dependency>
torsten@1:                     <groupId>org.jboss.as</groupId>
torsten@1:                     <artifactId>jboss-as-arquillian-container-managed</artifactId>
torsten@1:                     <scope>test</scope>
torsten@1:                 </dependency>
torsten@1:             </dependencies>
torsten@1:         </profile>
torsten@1: 
torsten@1:         <profile>
torsten@1:             <!-- An optional Arquillian testing profile that executes tests 
torsten@1:                 in a remote JBoss AS instance -->
torsten@1:             <!-- Run with: mvn clean test -Parq-jbossas-remote -->
torsten@1:             <id>arq-jbossas-remote</id>
torsten@1:             <dependencies>
torsten@1:                 <dependency>
torsten@1:                     <groupId>org.jboss.as</groupId>
torsten@1:                     <artifactId>jboss-as-arquillian-container-remote</artifactId>
torsten@1:                     <scope>test</scope>
torsten@1:                 </dependency>
torsten@1:             </dependencies>
torsten@1:         </profile>
torsten@1: 
torsten@1:         <profile>
torsten@1:             <!-- When built in OpenShift the 'openshift' profile will be 
torsten@1:                 used when invoking mvn. -->
torsten@1:             <!-- Use this profile for any OpenShift specific customization 
torsten@1:                 your app will need. -->
torsten@1:             <!-- By default that is to put the resulting archive into the 
torsten@1:                 'deployments' folder. -->
torsten@1:             <!-- http://maven.apache.org/guides/mini/guide-building-for-different-environments.html -->
torsten@1:             <id>openshift</id>
torsten@1:             <build>
torsten@1:                 <plugins>
torsten@1:                     <plugin>
torsten@1:                         <artifactId>maven-war-plugin</artifactId>
torsten@1:                         <version>2.1.1</version>
torsten@1:                         <configuration>
torsten@1:                             <outputDirectory>deployments</outputDirectory>
torsten@1:                             <warName>ROOT</warName>
torsten@1:                         </configuration>
torsten@1:                     </plugin>
torsten@1:                 </plugins>
torsten@1:             </build>
torsten@1:         </profile>
torsten@1: 
torsten@1:     </profiles>
torsten@1: </project>