forked from kiegroup/droolsjbpm-build-bootstrap
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathpom.xml
131 lines (119 loc) · 5.73 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
<?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.jboss</groupId>
<artifactId>jboss-parent</artifactId>
<!-- Keep in sync with the parent version in ../pom.xml (kie-parent) -->
<version>36</version>
<relativePath/>
</parent>
<groupId>org.kie</groupId>
<artifactId>kie-user-bom-parent</artifactId>
<packaging>pom</packaging>
<version>7.75.0-SNAPSHOT</version>
<name>KIE (Drools, jBPM) user BOM parent</name>
<description>
The user BOM parent is used to hold common configuration for all user BOMs. User BOMs can not directly extend
kie-parent as it brings lots of 3rd party versions in the dependencyManagement which is not desirable for user BOMs.
</description>
<url>http://www.kiegroup.org</url>
<inceptionYear>2001</inceptionYear>
<organization>
<name>JBoss by Red Hat</name>
<url>http://www.jboss.org/</url>
</organization>
<licenses>
<license>
<name>The Apache Software License, Version 2.0</name>
<url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
<scm>
<connection>scm:git:https://github.com/kiegroup/droolsjbpm-build-bootstrap.git</connection>
<developerConnection>scm:git:[email protected]:kiegroup/droolsjbpm-build-bootstrap.git</developerConnection>
<url>https://github.com/kiegroup/droolsjbpm-build-bootstrap</url>
</scm>
<ciManagement>
<system>jenkins</system>
<url>https://jenkins-kieci.rhcloud.com</url>
</ciManagement>
<properties>
<version.org.kie>${project.version}</version.org.kie>
<version.org.kie.lienzo>${version.org.kie}</version.org.kie.lienzo>
<version.org.optaplanner>7.73.0.Final</version.org.optaplanner>
<jboss.releases.repo.url>https://repository.jboss.org/nexus/service/local/staging/deploy/maven2/</jboss.releases.repo.url>
<jboss.snapshots.repo.url>https://repository.jboss.org/nexus/content/repositories/snapshots/</jboss.snapshots.repo.url>
</properties>
<repositories>
<!-- Having the <repositories> in this POM is an ugly hack to make sure we can always find
the jboss-integration-platform-parent (ip-parent). In most of the cases the ip-parent is available directly from
Maven Central. However, when new version gets released it takes up to 24 hours to get it synced into the Maven
Central. So in that period the local build of droolsjbpm-build-bootstrap would fail (unless one would
locally build the ip-parent from the sources as well, which is not something users should be doing). Configuring the
'repository.jboss.org' directly works around this issue. -->
<repository>
<!-- Duplicating the Maven Central repository here (as it is already coming from Super POM) makes the build much faster,
as the Maven Central is now treated as the first (default) repository (because it is before the JBoss.org one).
Artifacts with release (fixed) versions are being downloaded primarily from central. Without the central being the
first repository the JBoss.org Nexus would be contacted first and since it is quite slow it slows down the build.
We use JBoss.org repo only to download our SNAPSHOTs. -->
<id>central</id>
<name>Central Repository</name>
<url>https://repo.maven.apache.org/maven2</url>
<layout>default</layout>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<!-- Bootstrap repository to locate the parent pom when the parent pom has not been build locally. -->
<!-- Conventions are described in http://community.jboss.org/wiki/MavenGettingStarted-Developers -->
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>https://repository.jboss.org/nexus/content/groups/public/</url>
<releases>
<enabled>true</enabled>
<updatePolicy>never</updatePolicy>
</releases>
<snapshots>
<enabled>true</enabled>
<updatePolicy>daily</updatePolicy>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<!-- Duplicating the Maven Central repository here (as it is already coming from Super POM) makes the build much faster,
as the Maven Central is now treated as the first (default) repository (because it is before the JBoss.org one).
Artifacts with release (fixed) versions are being downloaded primarily from there. Without the central being the
first repository the JBoss.org Nexus would be contacted first and since it is quite slow it slows down the build.
We use JBoss.org repo only to download our SNAPSHOTs. -->
<id>central</id>
<name>Central Repository</name>
<url>https://repo.maven.apache.org/maven2</url>
<layout>default</layout>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>https://repository.jboss.org/nexus/content/groups/public/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
<!-- IMPORTANT: Do not declare any dependencies or dependency versions here! This POM should not contain any! -->
<dependencyManagement/>
<!-- Intentionally empty -->
<dependencies/>
<!-- Intentionally empty -->
</project>