forked from kiegroup/droolsjbpm-integration
-
Notifications
You must be signed in to change notification settings - Fork 1
/
pom.xml
166 lines (155 loc) · 5.61 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
<?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/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.kie</groupId>
<artifactId>kie-parent</artifactId>
<version>7.8.0-SNAPSHOT</version>
<!-- relativePath causes out-of-date problems on hudson slaves -->
<!--<relativePath>../droolsjbpm-build-bootstrap/pom.xml</relativePath>-->
</parent>
<groupId>org.drools</groupId>
<artifactId>droolsjbpm-integration</artifactId>
<packaging>pom</packaging>
<name>Drools and jBPM integration multiproject</name>
<description>
Drools and jBPM integration with seam, spring, camel, ...
</description>
<properties>
<findbugs.failOnViolation>true</findbugs.failOnViolation>
</properties>
<repositories>
<!-- Bootstrap repository to locate the parent pom when the parent pom has not been build locally. -->
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>https://repository.jboss.org/nexus/content/groups/public/</url>
<layout>default</layout>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
</repositories>
<scm>
<connection>scm:git:https://github.com:kiegroup/droolsjbpm-integration.git</connection>
<developerConnection>scm:git:git@github.com:kiegroup/droolsjbpm-integration.git</developerConnection>
<url>https://github.com/kiegroup/droolsjbpm-integration</url>
</scm>
<modules>
<module>kie-identity-session-provider</module>
<module>kie-maven-plugin</module>
<module>kie-takari-plugin</module>
<!-- The example can not be in the build because of the chicken-egg problem with depending on the plugin,
that is about to be build in the same Maven reactor build -->
<!--<module>kie-maven-plugin-example</module>-->
<module>drools-benchmark</module>
<!--<module>drools-simulator</module>-->
<module>drools-rhq-plugin</module>
<module>droolsjbpm-integration-examples</module>
<module>jbpm-simulation</module>
<module>kie-spring</module>
<module>kie-aries-blueprint</module>
<module>kie-eap-integration</module>
<module>kie-infinispan</module>
<module>drools-jboss-integration</module>
<module>kie-server-parent</module>
<module>jbpm-process-svg</module>
<module>kie-osgi</module>
<module>kie-performance-kit</module>
<module>drools-android</module>
<module>kie-security</module>
<module>kie-camel</module>
<module>kie-tomcat-integration</module>
<!-- The Android examples require Android SDK to be installed, so they are excluded from the default build -->
<!-- <module>drools-examples-android</module> -->
<module>kie-integration-test-coverage</module>
<module>kie-plugins-testing</module>
<module>kie-spring-boot</module>
</modules>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.drools</groupId>
<artifactId>drools-bom</artifactId>
<version>${version.org.kie}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.optaplanner</groupId>
<artifactId>optaplanner-bom</artifactId>
<version>${version.org.kie}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.jbpm</groupId>
<artifactId>jbpm-bom</artifactId>
<version>${version.org.kie}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.kie</groupId>
<artifactId>kie-dmn-bom</artifactId>
<version>${version.org.kie}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.uberfire</groupId>
<artifactId>uberfire-bom</artifactId>
<version>${version.org.uberfire}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.kie.soup</groupId>
<artifactId>kie-soup-bom</artifactId>
<version>${version.org.kie}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.kie</groupId>
<artifactId>kie-karaf-itests-domain-model</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<profiles>
<profile>
<id>fullProfile</id>
<activation>
<property>
<name>full</name>
</property>
</activation>
<modules>
<module>droolsjbpm-integration-distribution</module>
<module>droolsjbpm-bpms-distribution</module>
<module>droolsjbpm-brms-distribution</module>
</modules>
</profile>
<profile>
<id>android</id>
<!-- Do not active the profile automatically even if the ANDROID_HOME is set.
On most CI machines, the ANDROID_HOME is set, but the SDK is outdated and
the build then fails.
One needs to use "-Pandroid" explicitly to get the profile activated.
<activation>
<file><exists>${env.ANDROID_HOME}</exists></file>
</activation>
-->
<modules>
<module>drools-examples-android</module>
</modules>
</profile>
</profiles>
</project>