Project

General

Profile

Statistics
| Branch: | Tag: | Revision:

cdm-webapp / pom.xml @ 0a601525

History | View | Annotate | Download (6.85 KB)

1
<?xml version="1.0" encoding="UTF-8"?>
2
<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">
3
  <modelVersion>4.0.0</modelVersion>
4
  <artifactId>cdm-webapp</artifactId>
5
  <groupId>eu.etaxonomy</groupId>
6
  <version>4.5.1</version>
7
  <packaging>war</packaging>
8
  <name>CDM Webapp</name>
9
  <properties>
10
    <cdmlib.version>4.5.1</cdmlib.version>
11
    <cdm.vaadin.version>4.5.1</cdm.vaadin.version>
12
  </properties>
13
  <repositories>
14
    <!-- the cdm internal repository -->
15
    <repository>
16
      <id>EditRepository</id>
17
      <url>http://wp5.e-taxonomy.eu/mavenrepo/</url>
18
      <releases>
19
        <enabled>true</enabled>
20
        <updatePolicy>always</updatePolicy>
21
      </releases>
22
      <snapshots>
23
        <enabled>true</enabled>
24
        <updatePolicy>always</updatePolicy>
25
      </snapshots>
26
    </repository>
27
  </repositories>
28
  <distributionManagement>
29
    <repository>
30
      <uniqueVersion>false</uniqueVersion>
31
      <id>wp5.e-taxonomy.eu</id>
32
      <name>Edit Maven Repository</name>
33
      <url>scpexe://wp5.e-taxonomy.eu/var/www/wp5.e-taxonomy.eu/mavenrepo/</url>
34
      <layout>default</layout>
35
    </repository>
36
  </distributionManagement>
37
  <profiles>
38
    <profile>
39
      <id>local-repository</id>
40
      <activation>
41
        <property>
42
          <name>localrepo</name>
43
        </property>
44
      </activation>
45
      <repositories>
46
        <repository>
47
          <id>EditLocalRepository</id>
48
          <url>file://${localrepo}/eu/etaxonomy/</url>
49
          <releases>
50
            <enabled>false</enabled>
51
            <updatePolicy>always</updatePolicy>
52
          </releases>
53
          <snapshots>
54
            <enabled>true</enabled>
55
            <updatePolicy>always</updatePolicy>
56
          </snapshots>
57
        </repository>
58
      </repositories>
59
    </profile>
60
  </profiles>
61
  <dependencies>
62
    <dependency>
63
      <groupId>eu.etaxonomy</groupId>
64
      <artifactId>cdmlib-remote-webapp</artifactId>
65
      <version>${cdmlib.version}</version>
66
      <type>war</type>
67
    </dependency>
68
    <dependency>
69
      <groupId>eu.etaxonomy</groupId>
70
      <artifactId>cdm-vaadin</artifactId>
71
      <version>${cdm.vaadin.version}</version>
72
      <type>war</type>
73
    </dependency>
74
    <dependency>
75
      <groupId>eu.etaxonomy</groupId>
76
      <artifactId>cdmlib-db</artifactId>
77
      <version>${cdmlib.version}</version>
78
      <scope>test</scope>
79
    </dependency>
80
  </dependencies>
81
  <build>
82
    <plugins>
83
      <plugin>
84
        <groupId>org.apache.maven.plugins</groupId>
85
        <artifactId>maven-war-plugin</artifactId>
86
        <version>2.6</version>
87
        <configuration>
88
          <failOnMissingWebXml>flase</failOnMissingWebXml>
89
          <overlays>
90
            <!-- 
91
                Overlays are applied with a first-win strategy. 
92
                Overlays are applied in the order in which they are defined in the <overlays> configuration. 
93
                Therefore cdmlib-remote-webapp should come first.
94
                
95
                Once a change is made to any cdmlib-* project cdmlib should be build and the  
96
                cdmlib-remote-webapp.war will contain all these fresh artifacts. cdm-vaadin 
97
                in contrast is expected to be build only due to changes in the vaadin specific 
98
                code. The cdmlib-* artifact are excluded from the cdm-vaadin overlay to assure 
99
                that only the cdmlib-jars from cdm-remote-webapp can make their way into the final
100
                war.    
101
            -->
102
            <overlay>
103
              <!-- MUST BE THE FIRST war, see above -->
104
              <groupId>eu.etaxonomy</groupId>
105
              <artifactId>cdmlib-remote-webapp</artifactId>
106
            </overlay>
107
            <overlay>
108
              <groupId>eu.etaxonomy</groupId>
109
              <artifactId>cdm-vaadin</artifactId>
110
              <excludes>
111
                <exclude>WEB-INF/lib/cdmlib-*.jar</exclude>
112
              </excludes>
113
            </overlay>
114
          </overlays>
115
        </configuration>
116
      </plugin>
117
      <!-- 
118
        
119
        when executing the mvn deploy directly (not via jgit-flow *-finish) unpacked war
120
        resources are accumulating and must be deleted before entering the prepare-package
121
        life cycle phase, therefore configuring this auto-clean makes a lot of sense.
122
        
123
        BUT the auto-clean is causing problems with the jgit-flow plugin,
124
        it is called twice and thus removes the cdm-webapp-x.x.x.war after it has been build,
125
        maven then fails with : "The packaging for this project did not assign a file to the build artifact"
126
        Therefore this is disabled! 
127
        
128
        A possible solution to this is to bind define a special auto-clean execution to the prepare-package phase,
129
        as long as this plugin is defined before the maven-dependency-plugin the clean should only
130
        happen before the unpack, see http://www.mkyong.com/maven/maven-plugin-execution-order-in-same-phase/
131
        Maybe it makes sense to define a fileset that only includes the unpacked war files  
132
        
133
      <plugin>
134
        <groupId>org.apache.maven.plugins</groupId>
135
        <artifactId>maven-clean-plugin</artifactId>
136
        <version>2.5</version>
137
        <executions>
138
          <execution>
139
            <id>auto-clean</id>
140
            <phase>initialize</phase>
141
            <goals>
142
              <goal>clean</goal>
143
            </goals>
144
          </execution>
145
        </executions>
146
      </plugin>
147
        -->
148
      <plugin>
149
        <groupId>external.atlassian.jgitflow</groupId>
150
        <artifactId>jgitflow-maven-plugin</artifactId>
151
        <version>1.0-m6</version>
152
        <configuration>
153
          <pushHotfixes>true</pushHotfixes>
154
          <pushReleases>true</pushReleases>
155
          <enableSshAgent>true</enableSshAgent>
156
          <allowSnapshots>true</allowSnapshots>
157
          <allowUntracked>true</allowUntracked>
158
        </configuration>
159
        <dependencies>
160
          <!-- 
161
                upgrading dependency jsch.agent.version of jgit-flow plugin to 0.1.53 
162
                in order have ssl key exchange algorithms compatible with openssh 6.7 
163
          -->
164
          <dependency>
165
            <groupId>com.jcraft</groupId>
166
            <artifactId>jsch</artifactId>
167
            <version>0.1.53</version>
168
          </dependency>
169
        </dependencies>
170
      </plugin>
171
    </plugins>
172
    <extensions>
173
      <extension>
174
        <groupId>org.apache.maven.wagon</groupId>
175
        <artifactId>wagon-scm</artifactId>
176
        <version>2.10</version>
177
      </extension>
178
      <extension>
179
        <groupId>org.apache.maven.wagon</groupId>
180
        <artifactId>wagon-ssh</artifactId>
181
        <version>2.10</version>
182
      </extension>
183
      <extension>
184
        <groupId>org.apache.maven.wagon</groupId>
185
        <artifactId>wagon-ssh-external</artifactId>
186
        <version>2.10</version>
187
      </extension>
188
    </extensions>
189
  </build>
190
</project>
Add picture from clipboard (Maximum size: 40 MB)