-
Notifications
You must be signed in to change notification settings - Fork 10
Expand file tree
/
Copy pathpom.xml
More file actions
316 lines (308 loc) · 11.5 KB
/
pom.xml
File metadata and controls
316 lines (308 loc) · 11.5 KB
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
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
<?xml version="1.0"?>
<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>id.au.ringerc.testcase</groupId>
<artifactId>as7.eclipselink</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>jar</packaging>
<name>as7.eclipselink</name>
<url>http://maven.apache.org</url>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<eclipselink.version.2.3.stable>2.3.2</eclipselink.version.2.3.stable>
<eclipselink.version.2.3.milestone>2.3.3-M3</eclipselink.version.2.3.milestone>
<eclipselink.version.2.4.milestone>2.4.0</eclipselink.version.2.4.milestone>
<jboss.as.version>7.1.1.Final</jboss.as.version>
</properties>
<repositories>
<repository>
<id>eclipselink</id>
<url>http://www.eclipse.org/downloads/download.php?r=1&nf=1&file=/rt/eclipselink/maven.repo</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>org.eclipse.persistence</groupId>
<artifactId>eclipselink</artifactId>
<version>${eclipselink.version.2.4.milestone}</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.eclipse.persistence</groupId>
<artifactId>javax.persistence</artifactId>
<version>2.0.3</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.jboss.logging</groupId>
<artifactId>jboss-logging</artifactId>
<version>3.1.1.GA</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jboss-vfs</artifactId>
<version>3.1.0.Final</version>
<scope>provided</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.13.1</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.4</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
<compilerArguments>
<processor>org.eclipse.persistence.internal.jpa.modelgen.CanonicalModelProcessor</processor>
<Aeclipselink.persistencexml>src/main/java/META-INF/persistence.xml</Aeclipselink.persistencexml>
</compilerArguments>
</configuration>
</plugin>
</plugins>
</build>
<profiles>
<!--
When active, this profile adds static weaving support to the project,
working around the issues with broken dynamic weaving.
Activate this profile with "-Dprofile.static-weave -Dprofile.default"
The odd activation method is because we're using some activeByDefault
profiles to separate chunks of configuration. They're usually in
separate import poms and dependencyManagement, but that's not very
desirable for testcase distribution. Maven deactivates all
activeByDefault properties when an explicit profile is specified
and doesn't provide any magic profile name like "default" to say you
want to *add* the new profile to the already active set, hence this workaround.
Some additional classpath entries are required to permit
this weaver to run.
-->
<profile>
<id>static-weave</id>
<activation>
<property>
<name>profile.static-weave</name>
</property>
</activation>
<build>
<plugins>
<plugin>
<groupId>au.com.alderaan</groupId>
<artifactId>eclipselink-staticweave-maven-plugin</artifactId>
<version>1.0.3</version>
<executions>
<execution>
<goals>
<goal>weave</goal>
</goals>
<phase>process-classes</phase>
<configuration>
<logLevel>ALL</logLevel>
<persistenceXMLLocation>../../src/main/java/META-INF/persistence.xml</persistenceXMLLocation>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
<!--
arquillian-testing encapsulates all the Arquillian config
in a self-contained profile
-->
<profile>
<activation>
<activeByDefault>true</activeByDefault>
<property>
<name>profile.default</name>
</property>
</activation>
<id>arquillian-testing</id>
<dependencyManagement>
<dependencies>
<!-- Override dependency resolver with test version.
This must go *BEFORE* the Arquillian BOM. -->
<dependency>
<groupId>org.jboss.shrinkwrap.resolver</groupId>
<artifactId>shrinkwrap-resolver-bom</artifactId>
<version>2.0.0-alpha-1</version>
<scope>import</scope>
<type>pom</type>
</dependency>
<!-- Now pull in our server-based unit testing framework -->
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>1.0.0.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<!-- Arquillian test automation -->
<dependency>
<groupId>org.jboss.arquillian.junit</groupId>
<artifactId>arquillian-junit-container</artifactId>
<scope>test</scope>
</dependency>
<!-- And some additional ShrinkWrap descriptors that let us define
beans.xml etc at test time -->
<dependency>
<groupId>org.jboss.shrinkwrap.descriptors</groupId>
<artifactId>shrinkwrap-descriptors-impl-javaee</artifactId>
<scope>test</scope>
</dependency>
<!-- ShrinkWrap resolution of JAR libraries into WAR archive -->
<dependency>
<groupId>org.jboss.shrinkwrap.resolver</groupId>
<artifactId>shrinkwrap-resolver-impl-maven</artifactId>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>org.sonatype.sisu</groupId>
<artifactId>sisu-inject-plexus</artifactId>
</exclusion>
</exclusions>
</dependency>
<!-- Arquillian Persistence Extension for database testing -->
<dependency>
<groupId>org.jboss.arquillian.extension</groupId>
<artifactId>arquillian-persistence-impl</artifactId>
<version>1.0.0.Alpha4</version>
<scope>test</scope>
</dependency>
</dependencies>
</profile>
<!--
Profile that adds the JBoss AS 7 managed Arquillian container adapter
to the runtime classpath so Arquillian can test against JBoss AS 7.
This profile retains the test beans.xml and persistence.xml .
TODO: Should check out Arquillian Drone to remote control the webui
for functional testing.
-->
<profile>
<activation>
<activeByDefault>true</activeByDefault>
<property>
<name>profile.default</name>
</property>
</activation>
<id>jboss7-arq-remote</id>
<dependencies>
<dependency>
<groupId>org.jboss.as</groupId>
<artifactId>jboss-as-arquillian-container-remote</artifactId>
<version>${jboss.as.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
</profile>
<!--
Provide the Java EE APIs using JBoss's jboss-javaee-6.0 spec artifacts
-->
<profile>
<activation>
<activeByDefault>true</activeByDefault>
<property>
<name>profile.default</name>
</property>
</activation>
<id>jboss-javaee-dependencies</id>
<dependencyManagement>
<dependencies>
<!-- Use the JBoss JavaEE artifacts instead of the javax ones; see below -->
<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-6.0</artifactId>
<type>pom</type>
<version>3.0.0.Final</version>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<!--
DISABLED because these artifacts are cut-down archives
without any code and tend to cause failures when running
unit tests. We use the JBoss versions that have useful
stubs instead.
<dependency>
<groupId>javax</groupId>
<artifactId>javaee-api</artifactId>
<version>6.0</version>
</dependency>
-->
<!-- Use the JBoss java EE API packaging instead of
javax:javaee-api because the latter is a screwed up jar
with stripped-out methods that breaks with "absent code" errors
in exciting ways during certain uses. -->
<!-- We shouldn't really pull in the whole spec, only the bits we use, so
specify the APIs we use or expect to use explicitly -->
<dependency>
<groupId>org.jboss.spec.javax.ejb</groupId>
<artifactId>jboss-ejb-api_3.1_spec</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.interceptor</groupId>
<artifactId>jboss-interceptors-api_1.1_spec</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.el</groupId>
<artifactId>jboss-el-api_2.2_spec</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.transaction</groupId>
<artifactId>jboss-transaction-api_1.1_spec</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.ws.rs</groupId>
<artifactId>jboss-jaxrs-api_1.1_spec</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.xml.bind</groupId>
<artifactId>jboss-jaxb-api_2.2_spec</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.enterprise</groupId>
<artifactId>cdi-api</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.inject</groupId>
<artifactId>javax.inject</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.validation</groupId>
<artifactId>validation-api</artifactId>
</dependency>
</dependencies>
</profile>
</profiles>
</project>