...
| Code Block | ||
|---|---|---|
| ||
<?xml version="1.0" encoding="UTF-8"?>
<!-- See https://maven.apache.org/settings.html -->
<settings xmlns="http://maven.apache.org/SETTINGS/1.2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.2.0 https://maven.apache.org/xsd/settings-1.2.0.xsd">
<!-- Prefer Shibboleth hosted repositories -->
<activeProfiles>
<activeProfile>shib-repos</activeProfile>
</activeProfiles>
<!-- Required to deploy artifacts -->
<servers>
<server>
<id>release</id>
<username>USERNAME</username>
<password>PASSWORD</password>
</server>
<server>
<id>snapshot</id>
<username>USERNAME</username>
<password>PASSWORD</password>
</server>
<server>
<id>site</id>
<username>javasites</username>
<privateKey>${user.home}/.ssh/id_rsa</privateKey>
<passphrase>PASSPHRASE</passphrase>
</server>
</servers>
<profiles>
<!-- Required to deploy artifacts -->
<profile>
<id>release</id>
<properties>
<gpg.keyname>KEYNAME</gpg.keyname>
</properties>
</profile>
<!-- Shibboleth hosted repositories -->
<profile>
<id>shib-repos</id>
<!-- GEN-299 Remove Nexus from public internet
Requires SSH tunneling, for example :
ssh -L 1581:127.0.0.1:1581 -N shibboleth.net -f
If using Docker and/or local user is not the same as remote on shibboleth.net:
ssh -l <remote username> -L 1581:127.0.0.1:1581 -N shibboleth.net -f
-->
<properties>
<altReleaseDeploymentRepository>release::http://127.0.0.1:1581/nexus/content/repositories/releases</altReleaseDeploymentRepository>
<altSnapshotDeploymentRepository>snapshot::http://127.0.0.1:1581/nexus/content/repositories/snapshots</altSnapshotDeploymentRepository>
</properties>
<!-- If SSH tunneling is not possible (for example using Docker), use the following :
<properties>
<altReleaseDeploymentRepository>release::https://build.shibboleth.net/nexus-proxy/content/repositories/releases</altReleaseDeploymentRepository>
<altSnapshotDeploymentRepository>snapshot::https://build.shibboleth.net/nexus-proxy/content/repositories/snapshots</altSnapshotDeploymentRepository>
</properties>
-->
<repositories>
<repository>
<id>shib-releases</id>
<name>Shibboleth Releases Repository</name>
<url>https://build.shibboleth.net/maven/releases/</url>
<releases>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>shib-snapshots</id>
<name>Shibboleth Snapshots Repository</name>
<url>https://build.shibboleth.net/maven/snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
</repository>
<repository>
<id>shib-thirdparty</id>
<name>Shibboleth Thirdparty Repository</name>
<url>https://build.shibboleth.net/maven/thirdparty/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>shib-thirdparty-snapshots</id>
<name>Shibboleth Thirdparty Snapshots Repository</name>
<url>https://build.shibboleth.net/maven/thirdparty-snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
<checksumPolicy>fail</checksumPolicy>
</snapshots>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>shib-releases</id>
<name>Shibboleth Releases Repository</name>
<url>https://build.shibboleth.net/maven/releases/</url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>shib-snapshots</id>
<name>Shibboleth Snapshots Repository</name>
<url>https://build.shibboleth.net/maven/snapshots/</url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
<checksumPolicy>warn</checksumPolicy>
</snapshots>
</pluginRepository>
</pluginRepositories>
</profile>
</profiles>
<!-- This HTTPS mirror of Central may be required when building projects based on the V7 parent project.
For example, net.shibboleth.utilities.jetty9:jetty94-dta-ssl:1.0.0 which depends on net.shibboleth:parent:7.11.0
This is because the V7 parent project defines the Central repository URL using HTTP instead of HTTPS.
See https://maven.apache.org/docs/3.8.1/release-notes.html#how-to-fix-when-i-get-a-http-repository-blocked
-->
<!--
<mirrors>
<mirror>
<id>central-https</id>
<name>HTTPS mirror of HTTP Central</name>
<url>https://repo.maven.apache.org/maven2</url>
<mirrorOf>central</mirrorOf>
</mirror>
</mirrors>
-->
</settings> |
...