forked from uw-dims/tsk4j
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathpom.xml
87 lines (78 loc) · 2.82 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
<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>
<!--
This pom is purely a vehicle for copying TSK4j 3rd party
dependencies for users that DO have them built/installed into
this directory so that they can be added to git for users that
do NOT have them built/installed. It is NOT part of the TSK4j
codebase build process. We do NOT have the TSK4j super-pom for
a parent. Conversely, the parent pom does NOT list us as a
module.
-->
<!--
This pom uses a profile named 'repo' to copy the dependencies
listed below into the current directory (actually, under
target/dependency, the default for the dependency plugin).
Without this profile being activated, this pom acts on behalf of
the non-power user, and the package phase installs the required
jars+poms into the user's local repo (via use of the install
plugin). Note how in the install plugin configuration, we have
to supply exact pomFiles to be installed alongside the jar.
Without this, the pom found in the jar itself is NOT correctly
copied into the final repos, so dependency info is lost. This
is a known bug for the install plugin 2.5.2, see
http://jira.codehaus.org/browse/MINSTALL-110.
We use the dependency plugin's unpack-dependency goal to put the
required poms onto the local filessytem. All very ugly!
-->
<groupId>edu.uw.apl.commons</groupId>
<artifactId>tsk4j-local-repo-builder</artifactId>
<version>413.3.0</version>
<packaging>pom</packaging>
<name>
TSK4J - Local Repository Construction for Dependent Artifact Resolution
</name>
<dependencies>
<!-- Our armour module depends on this -->
<dependency>
<groupId>edu.uw.apl.commons</groupId>
<artifactId>shell-base</artifactId>
<version>1.0</version>
</dependency>
</dependencies>
<profiles>
<profile>
<id>repo</id>
<build>
<defaultGoal>process-sources</defaultGoal>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.9</version>
<executions>
<execution>
<id>copy-dependencies</id>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<useRepositoryLayout>true</useRepositoryLayout>
<copyPom>true</copyPom>
<addParentPoms>true</addParentPoms>
<includeGroupIds>
edu.uw.apl.commons
</includeGroupIds>
<outputDirectory>${project.basedir}</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>