forked from ccordenier/tapestry5-hotel-booking
-
Notifications
You must be signed in to change notification settings - Fork 0
/
pom.xml
executable file
·202 lines (184 loc) · 5.64 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
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
<project
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://maven.apache.org/POM/4.0.0">
<modelVersion>4.0.0</modelVersion>
<groupId>com.tap5.hotelbooking</groupId>
<artifactId>tapestry5-hotel-booking</artifactId>
<version>1.1-SNAPSHOT</version>
<packaging>war</packaging>
<name>tapestry5-hotel-booking Tapestry 5 Application</name>
<dependencies>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-core</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<!--
A dependency on either JUnit or TestNG is required, or the surefire
plugin (which runs the tests) will fail, preventing Maven from
packaging the WAR. Tapestry includes a large number of testing
facilities designed for use with TestNG (http://testng.org/), so it's
recommended.
-->
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>5.13.1</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.easymock</groupId>
<artifactId>easymock</artifactId>
<version>2.4</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-hibernate</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<dependency>
<groupId>com.h2database</groupId>
<artifactId>h2</artifactId>
<version>1.2.142</version>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-validator</artifactId>
<version>4.0.2.GA</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-beanvalidator</artifactId>
<version>${tapestry-release-version}</version>
</dependency>
<!--
tapestry-test will conflict with RunJettyRun inside Eclipse.
tapestry-test brings in Selenium, which is based on Jetty 5.1;
RunJettyRun uses Jetty 6.
-->
<dependency>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-test</artifactId>
<version>${tapestry-release-version}</version>
<scope>test</scope>
</dependency>
<!--
Provided by the servlet container, but sometimes referenced in the
application code.
-->
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>2.5</version>
<scope>provided</scope>
</dependency>
<!--
Tapx Core : include kaptcha component
-->
<dependency>
<groupId>com.howardlewisship</groupId>
<artifactId>tapx-core</artifactId>
<version>${tapx-release-version}</version>
</dependency>
<dependency>
<groupId>org.hibernate.javax.persistence</groupId>
<artifactId>hibernate-jpa-2.0-api</artifactId>
<version>1.0.0.Final</version>
</dependency>
</dependencies>
<build>
<finalName>tapestry5-hotel-booking</finalName>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<encoding>UTF-8</encoding>
<source>1.5</source>
<target>1.5</target>
<optimize>true</optimize>
</configuration>
</plugin>
<!-- Run the application using "mvn jetty:run" -->
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1.9</version>
<configuration>
<!-- Log to the console. -->
<requestLog implementation="org.mortbay.jetty.NCSARequestLog">
<!--
This doesn't do anything for Jetty, but is a workaround for a
Maven bug that prevents the requestLog from being set.
-->
<append>true</append>
</requestLog>
<systemProperties>
<systemProperty>
<name>tapestry.production-mode</name>
<value>false</value>
</systemProperty>
</systemProperties>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<suiteXmlFiles>
<suiteXmlFile>src/test/conf/testng.xml</suiteXmlFile>
</suiteXmlFiles>
<argLine>-Xmx500m -Dtapx.test-mode=true</argLine>
<redirectTestOutputToFile>false</redirectTestOutputToFile>
</configuration>
</plugin>
</plugins>
</build>
<reporting>
<!--
Adds a report detailing the components, mixins and base classes
defined by this module.
-->
<plugins>
<plugin>
<groupId>org.apache.tapestry</groupId>
<artifactId>tapestry-component-report</artifactId>
<version>${tapestry-release-version}</version>
<configuration>
<rootPackage>com.tap5.hotelbooking</rootPackage>
</configuration>
</plugin>
</plugins>
</reporting>
<repositories>
<!-- For snapshots of tynamo libraries -->
<repository>
<id>codehaus.snapshots</id>
<url>http://ci.repository.codehaus.org</url>
</repository>
<!-- For Shiro (and Tapestry) snapshots -->
<repository>
<id>apache-snapshots</id>
<url>http://repository.apache.org/snapshots/</url>
</repository>
<repository>
<id>apache</id>
<url>https://repository.apache.org/content/groups/public/</url>
</repository>
<repository>
<id>tapestry360-stable</id>
<url>http://tapestry.formos.com/maven-repository</url>
</repository>
<repository>
<id>tapestry360-snapshot</id>
<url>http://tapestry.formos.com/maven-snapshot-repository</url>
</repository>
</repositories>
<properties>
<tapx-release-version>1.1-SNAPSHOT</tapx-release-version>
<tapestry-release-version>5.2.2-SNAPSHOT</tapestry-release-version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
</project>