bordertech-parent
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>com.github.bordertech.common</groupId>
<artifactId>bordertech-parent</artifactId>
<version>1.0.21</version>
</dependency><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/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<name>bordertech-parent</name>
<groupId>com.github.bordertech.common</groupId>
<artifactId>bordertech-parent</artifactId>
<version>1.0.21</version>
<packaging>pom</packaging>
<properties>
<maven.compiler.target>1.8</maven.compiler.target>
<maven.compiler.source>1.8</maven.compiler.source>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<stagingBaseUrl>https://oss.sonatype.org/</stagingBaseUrl>
<stagingUrl>${stagingBaseUrl}service/local/staging/deploy/maven2/</stagingUrl>
<snapshotUrl>${stagingBaseUrl}content/repositories/snapshots</snapshotUrl>
<stagingId>ossrh</stagingId>
</properties>
<!--
Descendants MAY override the licence.
-->
<licenses>
<license>
<name>MIT License</name>
<url>https://github.com/bordertech/java-common/blob/master/LICENSE</url>
<distribution>manual</distribution>
<comments>MIT License</comments>
</license>
</licenses>
<!--
description is a required section for Maven Central.
Descendants SHOULD override the description.
-->
<description>
Common parent for BorderTech Maven projects.
This will help prevent BorderTech projects from bringing in multiple versions of the same dependencies.
It also helps configure projects which deploy artifacts to Maven Central.
</description>
<!--
url is a required section for Maven Central.
Descendants SHOULD override the url.
-->
<url>https://github.com/bordertech/java-common/</url>
<!--
Descendants outside the java-common project SHOULD override this section.
-->
<scm>
<url>https://github.com/bordertech/java-common</url>
<connection>scm:git:https://github.com/bordertech/java-common.git</connection>
<developerConnection>scm:git:https://github.com/bordertech/java-common.git</developerConnection>
<tag>bordertech-parent-1.0.21</tag>
</scm>
<!--
Descendants outside the java-common project SHOULD override this section.
-->
<issueManagement>
<system>GitHub</system>
<url>https://github.com/bordertech/java-common/issues</url>
</issueManagement>
<!--
Descendants outside the java-common project SHOULD override this section.
-->
<ciManagement>
<system>Github Actions</system>
<url>https://github.com/BorderTech/java-common/actions</url>
</ciManagement>
<!-- developers is a required section for Maven Central -->
<developers>
<developer>
<url>https://github.com/BorderTech</url>
</developer>
</developers>
<distributionManagement>
<snapshotRepository>
<id>${stagingId}</id>
<url>${snapshotUrl}</url>
</snapshotRepository>
<repository>
<id>${stagingId}</id>
<url>${stagingUrl}</url>
</repository>
</distributionManagement>
<build>
<pluginManagement>
<plugins>
<!-- Build jars. -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<configuration>
<archive>
<manifestEntries>
<Built-By /><!-- blank build user in manifest file -->
</manifestEntries>
</archive>
</configuration>
<executions>
<execution>
<id>test-jar</id>
<goals>
<goal>test-jar</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Assembly -->
<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<archive>
<manifestEntries>
<Built-By /><!-- blank build user in manifest file -->
</manifestEntries>
</archive>
</configuration>
</plugin>
<!-- Handle release. -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.5.3</version>
<configuration>
<autoVersionSubmodules>true</autoVersionSubmodules>
<useReleaseProfile>false</useReleaseProfile>
<!-- need this for gpg plugin to work correctly -->
<mavenExecutorId>forked-path</mavenExecutorId>
<releaseProfiles>release</releaseProfiles>
</configuration>
</plugin>
</plugins>
</pluginManagement>
<plugins>
<!-- Compile the java source. -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.10.1</version>
</plugin>
<!-- Javadoc -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>3.4.1</version>
<configuration>
<archive>
<manifestEntries>
<Built-By /><!-- blank build user in manifest file -->
</manifestEntries>
</archive>
<charset>UTF-8</charset>
<encoding>UTF-8</encoding>
<docencoding>UTF-8</docencoding>
<breakiterator>true</breakiterator>
<version>true</version>
<keywords>true</keywords>
</configuration>
<executions>
<execution>
<!-- A release to Maven Central MUST include javadoc Jars - even if they are dummy jars -->
<id>attach-javadocs</id>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
<!-- Enforcer -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>3.5.0</version>
<executions>
<execution>
<id>enforcer</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireMavenVersion>
<version>[3.6.3,)</version>
</requireMavenVersion>
<requireJavaVersion>
<version>[1.8,)</version>
</requireJavaVersion>
<requirePropertyDiverges>
<property>project.description</property>
</requirePropertyDiverges>
</rules>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.codehaus.mojo</groupId>
<artifactId>extra-enforcer-rules</artifactId>
<version>1.8.0</version>
</dependency>
</dependencies>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<!--
The build cannot release to maven central without configuring several secrets in settings.xml
Read here: https://github.com/BorderTech/wcomponents/wiki/Releasing
-->
<id>release</id>
<build>
<plugins>
<!--
Create jar of the source files.
This is required for release to Maven repo.
-->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<version>3.2.1</version>
<configuration>
<archive>
<manifestEntries>
<Built-By /><!-- blank build user in manifest file -->
</manifestEntries>
</archive>
<includes>
<include>**/*.java</include>
</includes>
</configuration>
<executions>
<execution>
<id>sources</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
<execution>
<id>test-sources</id>
<phase>package</phase>
<goals>
<goal>test-jar</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-gpg-plugin</artifactId>
<version>3.0.1</version>
<executions>
<execution>
<id>sign-artifacts</id>
<phase>verify</phase>
<goals>
<goal>sign</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<modules>
<!--
Why not use a separate aggregator POM?
Because you are forced to configure the release plugin in both places - pointless duplication.
-->
<module>build-tools</module>
<module>qa-parent</module>
</modules>
</project>
Open source consumption has exploded, with estimates placing this year’s downloads at over 6.6 trillion. This reliance on open source components, now making up to 90% of the modern software application, has ushered in both unprecedented innovation and complex challenges for software supply chains.
View the Report