-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathpom.xml
172 lines (138 loc) · 7.02 KB
/
pom.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.movies</groupId>
<artifactId>movies</artifactId>
<version>1.0-SNAPSHOT</version>
<modules>
<module>database</module>
</modules>
<packaging>pom</packaging>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.source>1.7</maven.compiler.source>
<maven.compiler.target>1.7</maven.compiler.target>
<!-- The standardized API -->
<hibernate.jpa21.api.version>1.0.0.Final</hibernate.jpa21.api.version>
<!-- Hibernate's implementation -->
<hibernate.version>5.0.1.Final</hibernate.version>
<!-- The standardized Bean Validation API -->
<validation.api.version>1.1.0.Final</validation.api.version>
<!-- Hibernate's implementation -->
<hibernate.validator.version>5.2.1.Final</hibernate.validator.version>
<javax-el.version>3.0.1-b04</javax-el.version>
<!-- Everyone's favorite -->
<slf4j.impl.version>1.6.1</slf4j.impl.version>
<!-- For small scale deployment, use the H2 RDBMS, all Java -->
<h2.version>1.3.171</h2.version>
<!-- In Java SE you should use a JTA transaction manager as a JDBC connection pool, Bitronix is good -->
<btm.version>2.1.3</btm.version>
<!-- Integration testing with TestNG is easier than JUnit -->
<testng.version>6.8.7</testng.version>
<!-- Java EE 7 API for the application examples -->
<javaee-api.version>7.0</javaee-api.version>
<!-- Application examples integration testing with Java EE environment -->
<shrinkwrap.version>2.0.2</shrinkwrap.version>
<arquillian.version>1.0.4.Final</arquillian.version>
<arquillian.extension.persistence.version>1.0.0.Alpha6</arquillian.extension.persistence.version>
<arquillian.extension.rest.version>1.0.0.Alpha3</arquillian.extension.rest.version>
<dbunit.version>2.4.9</dbunit.version>
<wildfly.version>8.1.0.Final</wildfly.version>
<!-- Wildfly server deployment plugin for the application examples -->
<wildfly.maven-plugin.version>1.0.2.Final</wildfly.maven-plugin.version>
</properties>
<build>
<pluginManagement>
<plugins>
<!-- Hibernate bytecode enhancer plugin
TODO https://hibernate.atlassian.net/browse/HHH-7963 -->
<plugin>
<groupId>org.hibernate.orm.tooling</groupId>
<artifactId>hibernate-enhance-maven-plugin</artifactId>
<version>${hibernate.version}</version>
<dependencies>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-entitymanager</artifactId>
<version>${hibernate.version}</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-validator</artifactId>
<version>${hibernate.validator.version}</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-envers</artifactId>
<version>${hibernate.version}</version>
</dependency>
</dependencies>
<executions>
<execution>
<phase>process-classes</phase>
<goals>
<goal>enhance</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.9</version>
<configuration>
<redirectTestOutputToFile>true</redirectTestOutputToFile>
<!-- If you enable the 'app' module tests, you need to configure this -->
<environmentVariables>
<JBOSS_HOME>/Users/cb/work/jboss/server/current</JBOSS_HOME>
</environmentVariables>
<systemPropertyVariables>
<derby.stream.error.field>java.lang.System.err</derby.stream.error.field>
<java.util.logging.config.file>../shared/src/main/resources/logging.properties</java.util.logging.config.file>
</systemPropertyVariables>
<suiteXmlFiles>
<suiteXmlFile>src/test/AllTests.tng.xml</suiteXmlFile>
</suiteXmlFiles>
</configuration>
</plugin>
<!-- For the application examples, we need WAR packaging -->
<plugin>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
<configuration>
<!-- WARs no longer have this file in 2014 -->
<failOnMissingWebXml>false</failOnMissingWebXml>
<!-- Also attach JAR so we can easily depend on the WAR in (EJB) client modules -->
<attachClasses>true</attachClasses>
<!-- An exploded WAR directory must be named .war or Wildfly won't deploy it -->
<webappDirectory>${project.build.directory}/${project.artifactId}-exploded.war</webappDirectory>
<!-- No version number -->
<warName>${project.artifactId}</warName>
</configuration>
</plugin>
<!-- We want to disable Maven deployment for some modules -->
<plugin>
<artifactId>maven-deploy-plugin</artifactId>
<version>2.7</version>
</plugin>
</plugins>
</pluginManagement>
</build>
<!-- ##################################################################################################### -->
<reporting>
<excludeDefaults>true</excludeDefaults>
</reporting>
<!-- ##################################################################################################### -->
<profiles>
<profile>
<id>real</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<modules>
<module>database</module>
</modules>
</profile>
</profiles>
</project>