-
Notifications
You must be signed in to change notification settings - Fork 26
/
pom.xml
160 lines (150 loc) · 6.15 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
<?xml version="1.0" encoding="UTF-8"?>
<!--
~ The MIT License
~
~ Copyright (c) 2016-2021, CloudBees, Inc.
~
~ Permission is hereby granted, free of charge, to any person obtaining a copy
~ of this software and associated documentation files (the "Software"), to deal
~ in the Software without restriction, including without limitation the rights
~ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
~ copies of the Software, and to permit persons to whom the Software is
~ furnished to do so, subject to the following conditions:
~
~ The above copyright notice and this permission notice shall be included in
~ all copies or substantial portions of the Software.
~
~ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
~ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
~ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
~ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
~ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
~ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
~ THE SOFTWARE.
-->
<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.jenkins-ci.plugins</groupId>
<artifactId>plugin</artifactId>
<version>5.4</version>
<relativePath />
</parent>
<artifactId>bouncycastle-api</artifactId>
<version>2.30.${revision}-${changelist}</version>
<packaging>hpi</packaging>
<name>bouncycastle API Plugin</name>
<description>This plugin provides an stable API to Bouncy Castle related tasks.</description>
<url>https://github.com/jenkinsci/bouncycastle-api-plugin</url>
<licenses>
<license>
<name>The MIT license</name>
<url>https://www.opensource.org/licenses/mit-license.php</url>
<distribution>repo</distribution>
</license>
</licenses>
<developers>
<developer>
<id>alvarolobato</id>
<name>Alvaro Lobato</name>
<email>[email protected]</email>
</developer>
</developers>
<scm>
<connection>scm:git:https://github.com/jenkinsci/bouncycastle-api-plugin.git</connection>
<developerConnection>scm:git:[email protected]:jenkinsci/bouncycastle-api-plugin.git</developerConnection>
<tag>${scmTag}</tag>
<url>https://github.com/jenkinsci/bouncycastle-api-plugin</url>
</scm>
<properties>
<revision>1.79</revision>
<changelist>999999-SNAPSHOT</changelist>
<jenkins.version>2.479.1</jenkins.version>
<useBeta>true</useBeta>
<spotless.check.skip>false</spotless.check.skip>
</properties>
<dependencies>
<!--
The BouncyCastle jars are exposed as regular dependencies to other plugins who depend on this plugin on the build classpath.
The JARs are not added to the plugin in the normal way though, rather they are conditionally injected into the classpath at initialisation time.
This allows plugin compilation etc to work as normal, however if the JVM has been configured using BouncyCastle FIPS jars for FIPS compliance we will not inject
incompatible classes or try to register a non fips compliant Provider.
The FIPS and non FIPS versions of BouncyCastle are mostly but not completely API compatible if the consumer steers clear of any deprecated APIs or low level APIS.
This may cause some plugins that depend on this to blow up at runtime (e.g SAML), but without this even more things would go bang.
-->
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcpkix-jdk18on</artifactId>
<version>${revision}</version>
</dependency>
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk18on</artifactId>
<version>${revision}</version>
</dependency>
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcutil-jdk18on</artifactId>
<version>${revision}</version>
</dependency>
<dependency>
<groupId>org.assertj</groupId>
<artifactId>assertj-core</artifactId>
<version>3.26.3</version>
<scope>test</scope>
</dependency>
</dependencies>
<repositories>
<repository>
<id>repo.jenkins-ci.org</id>
<url>https://repo.jenkins-ci.org/public/</url>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>repo.jenkins-ci.org</id>
<url>https://repo.jenkins-ci.org/public/</url>
</pluginRepository>
</pluginRepositories>
<build>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<reuseForks>false</reuseForks>
</configuration>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<!-- copy the bouncycastle jars so they will be in the java archive -->
<id>copy-bc-jars</id>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<includeGroupIds>org.bouncycastle</includeGroupIds>
<excludeTransitive>true</excludeTransitive>
<outputDirectory>${project.build.directory}/extra-classes/WEB-INF/optional-lib/</outputDirectory>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.jenkins-ci.tools</groupId>
<artifactId>maven-hpi-plugin</artifactId>
<configuration>
<!-- do not add bouncycastle jars to WEB-INF/lib as they get added dynamically to be compatible with bouncycastle fips-->
<warSourceExcludes>WEB-INF/lib/bc*.jar</warSourceExcludes>
<!-- and add them back in but in so they are in WEB-INF/optional-lib/ so we can load them dynamically -->
<webappDirectory>${project.build.directory}/extra-classes/</webappDirectory>
</configuration>
</plugin>
</plugins>
</build>
</project>