-
Notifications
You must be signed in to change notification settings - Fork 0
/
pom.xml
225 lines (220 loc) · 8.11 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
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
<?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>
<artifactId>cdm-webapp</artifactId>
<groupId>eu.etaxonomy</groupId>
<version>5.46.0-SNAPSHOT</version>
<packaging>war</packaging>
<name>CDM Webapp</name>
<properties>
<cdmlib.version>5.46.0-SNAPSHOT</cdmlib.version>
<cdm.vaadin.version>5.46.0-SNAPSHOT</cdm.vaadin.version>
</properties>
<repositories>
<!-- the cdm internal repository -->
<repository>
<id>EditRepository</id>
<url>https://cybertaxonomy.org/mavenrepo</url>
<releases>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</snapshots>
</repository>
</repositories>
<distributionManagement>
<repository>
<uniqueVersion>false</uniqueVersion>
<id>cybertaxonomy.eu</id>
<name>Edit Maven Repository</name>
<url>scpexe://cybertaxonomy.org/var/www/wp5.e-taxonomy.eu/mavenrepo/</url>
<layout>default</layout>
</repository>
</distributionManagement>
<profiles>
<profile>
<id>local-repository</id>
<activation>
<property>
<name>localrepo</name>
</property>
</activation>
<repositories>
<repository>
<id>EditLocalRepository</id>
<url>file://${localrepo}/eu/etaxonomy/</url>
<releases>
<enabled>false</enabled>
<updatePolicy>always</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>always</updatePolicy>
</snapshots>
</repository>
</repositories>
</profile>
</profiles>
<dependencies>
<dependency>
<groupId>eu.etaxonomy</groupId>
<artifactId>cdmlib-remote-webapp</artifactId>
<version>${cdmlib.version}</version>
<type>war</type>
</dependency>
<dependency>
<groupId>eu.etaxonomy</groupId>
<artifactId>cdm-vaadin</artifactId>
<version>${cdm.vaadin.version}</version>
<type>war</type>
</dependency>
<dependency>
<groupId>eu.etaxonomy</groupId>
<artifactId>cdmlib-db</artifactId>
<version>${cdmlib.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>3.3.2</version>
<configuration>
<failOnMissingWebXml>flase</failOnMissingWebXml>
<overlays>
<!--
Overlays are applied with a first-win strategy.
Overlays are applied in the order in which they are defined in the <overlays> configuration.
Therefore cdmlib-remote-webapp should come first.
Once a change is made to any cdmlib-* project cdmlib should be build and the
cdmlib-remote-webapp.war will contain all these fresh artifacts. cdm-vaadin
in contrast is expected to be build only due to changes in the vaadin specific
code. The cdmlib-* artifact are excluded from the cdm-vaadin overlay to assure
that only the cdmlib-jars from cdm-remote-webapp can make their way into the final
war.
-->
<overlay>
<!-- MUST BE THE FIRST war, see above -->
<groupId>eu.etaxonomy</groupId>
<artifactId>cdmlib-remote-webapp</artifactId>
</overlay>
<overlay>
<groupId>eu.etaxonomy</groupId>
<artifactId>cdm-vaadin</artifactId>
<excludes>
<exclude>WEB-INF/lib/cdmlib-*.jar</exclude>
</excludes>
</overlay>
<overlay>
<!-- overlay a second time to only add cdmlib-cache.jar -->
<groupId>eu.etaxonomy</groupId>
<artifactId>cdm-vaadin</artifactId>
<includes>
<include>WEB-INF/lib/cdmlib-cache*.jar</include>
</includes>
</overlay>
</overlays>
</configuration>
</plugin>
<!--
when executing the mvn deploy directly (not via jgit-flow *-finish) unpacked war
resources are accumulating and must be deleted before entering the prepare-package
life cycle phase, therefore configuring this auto-clean makes a lot of sense.
BUT the auto-clean is causing problems with the jgit-flow plugin,
it is called twice and thus removes the cdm-webapp-x.x.x.war after it has been build,
maven then fails with : "The packaging for this project did not assign a file to the build artifact"
Therefore this is disabled!
A possible solution to this is to bind define a special auto-clean execution to the prepare-package phase,
as long as this plugin is defined before the maven-dependency-plugin the clean should only
happen before the unpack, see http://www.mkyong.com/maven/maven-plugin-execution-order-in-same-phase/
Maybe it makes sense to define a fileset that only includes the unpacked war files
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<version>2.5</version>
<executions>
<execution>
<id>auto-clean</id>
<phase>initialize</phase>
<goals>
<goal>clean</goal>
</goals>
</execution>
</executions>
</plugin>
-->
<plugin>
<!-- groupId>ch.dvbern.oss.maven.jgitflow</groupId>
<artifactId>jgitflow-maven-plugin</artifactId>
<version>1.0-m8</version> -->
<groupId>external.atlassian.jgitflow</groupId>
<artifactId>jgitflow-maven-plugin</artifactId>
<version>1.0-m6</version>
<configuration>
<pushHotfixes>true</pushHotfixes>
<pushReleases>true</pushReleases>
<enableSshAgent>true</enableSshAgent>
<allowSnapshots>true</allowSnapshots>
<allowUntracked>true</allowUntracked>
</configuration>
<dependencies>
<!--
upgrading dependency jsch.agent.version of jgit-flow plugin to 0.1.53
in order have ssl key exchange algorithms compatible with openssh 6.7
-->
<dependency>
<groupId>com.jcraft</groupId>
<artifactId>jsch</artifactId>
<version>0.1.55</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>3.1.0</version>
<executions>
<execution>
<id>enforce</id>
<configuration>
<fail>true</fail>
<skip>false</skip>
<rules>
<dependencyConvergence />
<requireMavenVersion>
<version>[3.6.0,)</version>
</requireMavenVersion>
</rules>
</configuration>
<goals>
<goal>enforce</goal>
<!-- Binds by default to the lifecycle phase: validate -->
</goals>
</execution>
</executions>
</plugin>
</plugins>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-scm</artifactId>
<version>3.5.1</version>
</extension>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh</artifactId>
<version>3.5.1</version>
</extension>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
<version>3.5.1</version>
</extension>
</extensions>
</build>
</project>