pom.xml 1.77 KB
Newer Older
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
<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/maven-v4_0_0.xsd">

  <modelVersion>4.0.0</modelVersion>
  <artifactId>org.fortiss.af3.tests</artifactId>
  <groupId>org.fortiss.af3.tests</groupId>
  <packaging>pom</packaging>

  <parent>
    <groupId>org.fortiss.af3</groupId>
    <artifactId>org.fortiss.af3.root</artifactId>
    <version>1.0.0-SNAPSHOT</version>
    <relativePath>../pom.xml</relativePath>
  </parent>

  <profiles>
    <profile>
      <id>af3-p2-local</id>
      <activation>
        <property>
          <name>!af3</name>
        </property>
      </activation>
      <repositories>
        <repository>
          <!-- Place more centrally and combine with af3 profile -->
          <id>af3-p2</id>
          <layout>p2</layout>
          <!-- In jenkins, the tooling update site must be copied to this location. -->
Alexander Diewald's avatar
Alexander Diewald committed
32
          <url>file:${user.dir}/releng/org.fortiss.af3.update/target/repository/</url>
33
34
35
        </repository>
      </repositories>
    </profile>
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
    <!-- For local debugging, the profiles "af3" and "tooling" can be used such that source code
         changes are immediately picked up. In the default case, the product produced by
         "mvn verify -Paf3,tooling,emf-generation" is used (esp. in Jenkins).
         See the developer documentation about debugging maven integration tests locally. -->
    <profile>
      <id>af3</id>
      <modules>
        <module>../bundles/af3</module>
      </modules>
    </profile>
    <profile>
      <id>tooling</id>
      <modules>
        <module>../bundles/kernel</module>
      </modules>
    </profile>
52
53
  </profiles>
</project>