forked from sonatype/tycho-extras
-
Notifications
You must be signed in to change notification settings - Fork 0
/
pom.xml
74 lines (68 loc) · 2.21 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
<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>
<parent>
<groupId>org.sonatype.tycho</groupId>
<artifactId>tycho-extras</artifactId>
<version>0.12.0-SNAPSHOT</version>
</parent>
<artifactId>tycho-p2-extras-plugin</artifactId>
<packaging>maven-plugin</packaging>
<name>Tycho P2 Extras Plugin</name>
<properties>
<tycho-build-version>${project.version}</tycho-build-version>
</properties>
<dependencies>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-plugin-api</artifactId>
</dependency>
<dependency>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-p2-facade</artifactId>
<version>${tycho-version}</version>
</dependency>
<dependency>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-testing-harness</artifactId>
<version>${tycho-version}</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.sonatype.plugins</groupId>
<artifactId>maven-properties-plugin</artifactId>
<version>0.0.2</version>
<executions>
<execution>
<phase>process-test-resources</phase>
<goals>
<goal>filter-file</goal>
</goals>
<configuration>
<in>src/test/resources/baseTest.properties</in>
<outDir>target/test-classes/</outDir>
</configuration>
</execution>
</executions>
</plugin>
<!-- During the unit tests, the test project is copied to the target folder and the
publish mojo is executed on the project. The test project may also be built
directly from the command line. This configuration makes sure that the target
folder from a direct invocation is removed. Otherwise it may iterfere with the
target folder created during the unit tests. -->
<plugin>
<artifactId>maven-clean-plugin</artifactId>
<configuration>
<filesets>
<fileset>
<directory>src/test/resources/testProject/target</directory>
</fileset>
</filesets>
</configuration>
</plugin>
</plugins>
</build>
</project>