You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by se...@apache.org on 2019/08/17 15:52:53 UTC
[commons-parent] branch master updated: Standardise section order
This is an automated email from the ASF dual-hosted git repository.
sebb pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-parent.git
The following commit(s) were added to refs/heads/master by this push:
new 0e979bf Standardise section order
0e979bf is described below
commit 0e979bf6e1653bf4a429fca20796c0581da16487
Author: Sebb <se...@apache.org>
AuthorDate: Sat Aug 17 16:52:45 2019 +0100
Standardise section order
---
pom.xml => pom.sav | 0
pom.xml | 509 +++++++++++++++++++++++++++--------------------------
2 files changed, 256 insertions(+), 253 deletions(-)
diff --git a/pom.xml b/pom.sav
similarity index 100%
copy from pom.xml
copy to pom.sav
diff --git a/pom.xml b/pom.xml
index fbbe850..a2b3e6b 100644
--- a/pom.xml
+++ b/pom.xml
@@ -27,24 +27,11 @@
</parent>
<groupId>org.apache.commons</groupId>
<artifactId>commons-parent</artifactId>
- <packaging>pom</packaging>
<version>49-SNAPSHOT</version>
+ <packaging>pom</packaging>
<name>Apache Commons Parent</name>
- <url>https://commons.apache.org/commons-parent-pom.html</url>
<description>The Apache Commons Parent POM provides common settings for all Apache Commons components.</description>
- <issueManagement>
- <system>jira</system>
- <url>https://issues.apache.org/jira/browse/COMMONSSITE</url>
- </issueManagement>
-
- <prerequisites>
- <maven>3.0.5</maven>
- </prerequisites>
-
- <ciManagement>
- <system>jenkins</system>
- <url>https://builds.apache.org/</url>
- </ciManagement>
+ <url>https://commons.apache.org/commons-parent-pom.html</url>
<!--
In release 31, the maven.compile.* properties were corrected to maven.compiler.*
@@ -95,15 +82,235 @@
-->
- <!--
- This section *must* be overwritten by subprojects. It is only to allow
- a release of the commons-parent POM.
- -->
- <scm>
- <connection>scm:git:http://gitbox.apache.org/repos/asf/commons-parent.git</connection>
- <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/commons-parent.git</developerConnection>
- <url>https://gitbox.apache.org/repos/asf?p=commons-parent.git</url>
- </scm>
+
+ <properties>
+ <!-- configuration bits for cutting a release candidate, must be overridden by components -->
+ <commons.release.version>${project.version}</commons.release.version>
+ <commons.rc.version>RC1</commons.rc.version>
+ <commons.jira.id>COMMONSSITE</commons.jira.id>
+
+ <!-- Default configuration for compiler source and target JVM -->
+ <!-- Do NOT change this; it must remain as 1.3 -->
+ <!--
+ It's important that child POMs don't need to change when the parent POM is updated.
+ At the time when these properties were introduced, the default Java version was 1.3.
+ Thus components that failed to define the version would not be affected by updates
+ to the Commons Parent or its parent the Apache pom.
+ Of course most if not all components now define the properties.
+ However it's still important to keep the properties as they effectively
+ force child poms to define the Java version they require.
+ -->
+ <maven.compiler.source>1.3</maven.compiler.source>
+ <maven.compiler.target>1.3</maven.compiler.target>
+
+ <!-- compiler and surefire plugin settings for "java" profiles -->
+ <commons.compiler.fork>false</commons.compiler.fork>
+ <commons.compiler.compilerVersion />
+ <commons.compiler.javac />
+
+ <!-- plugin versions (allows same value in reporting and build sections; also allows easy override) -->
+ <commons.build-plugin.version>1.10</commons.build-plugin.version>
+ <commons.release-plugin.version>1.6</commons.release-plugin.version>
+ <commons.surefire.version>2.22.2</commons.surefire.version>
+ <commons.failsafe.version>2.22.2</commons.failsafe.version>
+ <commons.surefire-report.version>2.22.2</commons.surefire-report.version>
+ <commons.javadoc.version>3.1.1</commons.javadoc.version>
+ <commons.rat.version>0.13</commons.rat.version>
+ <commons.changes.version>2.12.1</commons.changes.version>
+ <commons.clirr.version>2.8</commons.clirr.version>
+ <commons.japicmp.version>0.14.1</commons.japicmp.version>
+ <commons.jxr.version>3.0.0</commons.jxr.version>
+ <commons.project-info.version>3.0.0</commons.project-info.version>
+ <commons.wagon-ssh.version>3.3.3</commons.wagon-ssh.version>
+ <!--
+ Note: Maven site plugin 3.5.1 is the latest version but is not a direct replacement:
+
+ https://maven.apache.org/plugins/maven-site-plugin/migrate.html
+
+ In particular, adding CDATA to header and footer sections is not backwards compatible.
+ I.e. these have to be updated at the same time.
+
+ Also it causes the following errors:
+
+ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on project commons-parent:
+ Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.5.1:site failed:
+ A required class was missing while executing org.apache.maven.plugins:maven-site-plugin:3.5.1:site: org/apache/maven/doxia/sink/impl/XhtmlBaseSink
+
+ This is because Apache POM 17 forces an older version of Doxia core:
+ https://mail-archives.apache.org/mod_mbox/maven-users/201602.mbox/%3C2337255.xU7aS9G1qr@herve-desktop%3E
+
+ The same error applies when running with version 3.5.
+
+ Since the version is defined as a property, the CP version can be overridden as follows if necessary:
+
+ mvn site -Dcommons.site-plugin.version=3.5.1
+
+ You will also need to add a dependency on Doxia core:
+ <artifactId>maven-site-plugin</artifactId>
+ <dependencies>
+ <dependency>
+ <groupId>org.apache.maven.doxia</groupId>
+ <artifactId>doxia-core</artifactId>
+ <version>1.8</version>
+ </dependency>
+ </dependencies>
+
+ -->
+ <commons.source-plugin.version>3.1.0</commons.source-plugin.version>
+ <commons.checkstyle-plugin.version>3.1.0</commons.checkstyle-plugin.version>
+ <commons.jar-plugin.version>3.1.2</commons.jar-plugin.version>
+ <commons.assembly-plugin.version>3.1.1</commons.assembly-plugin.version>
+ <commons.site-plugin.version>3.7.1</commons.site-plugin.version>
+ <commons.jacoco.version>0.8.3</commons.jacoco.version>
+ <commons.cobertura.version>2.7</commons.cobertura.version>
+ <commons.coveralls.version>4.3.0</commons.coveralls.version>
+ <commons.coveralls.timestampFormat>EpochMillis</commons.coveralls.timestampFormat>
+ <commons.jdepend.version>2.0</commons.jdepend.version>
+ <commons.compiler.version>3.8.1</commons.compiler.version>
+ <commons.scm-publish.version>1.1</commons.scm-publish.version>
+ <commons.findbugs.version>3.0.5</commons.findbugs.version>
+ <commons.spotbugs.version>3.1.6</commons.spotbugs.version>
+ <commons.pmd.version>3.12.0</commons.pmd.version>
+ <commons.felix.version>4.2.0</commons.felix.version>
+ <commons.build-helper.version>3.0.0</commons.build-helper.version>
+ <commons.animal-sniffer.version>1.17</commons.animal-sniffer.version>
+ <!-- Almost all signatures use version 1.0. Allow override just in case -->
+ <commons.animal-sniffer.signature.version>1.0</commons.animal-sniffer.signature.version>
+
+ <!-- Default values for the download-page generation by commons-build-plugin -->
+ <commons.release.name>${project.artifactId}-${commons.release.version}</commons.release.name>
+ <commons.release.desc />
+ <commons.binary.suffix>-bin</commons.binary.suffix>
+ <commons.release.2.name>${project.artifactId}-${commons.release.2.version}</commons.release.2.name>
+ <commons.release.2.desc />
+ <commons.release.2.binary.suffix>-bin</commons.release.2.binary.suffix>
+ <commons.release.3.name>${project.artifactId}-${commons.release.3.version}</commons.release.3.name>
+ <commons.release.3.desc />
+ <commons.release.3.binary.suffix>-bin</commons.release.3.binary.suffix>
+ <commons.release.4.desc />
+ <commons.release.4.binary.suffix>-bin</commons.release.4.binary.suffix>
+
+ <!-- Default values for the jacoco-maven-plugin reports -->
+ <commons.jacoco.classRatio>1.00</commons.jacoco.classRatio>
+ <commons.jacoco.instructionRatio>0.90</commons.jacoco.instructionRatio>
+ <commons.jacoco.methodRatio>0.95</commons.jacoco.methodRatio>
+ <commons.jacoco.branchRatio>0.85</commons.jacoco.branchRatio>
+ <commons.jacoco.complexityRatio>0.85</commons.jacoco.complexityRatio>
+ <commons.jacoco.lineRatio>0.90</commons.jacoco.lineRatio>
+ <commons.jacoco.haltOnFailure>false</commons.jacoco.haltOnFailure>
+
+ <!-- The Commons component id is used on the distribution server, for example:
+ - Use dbcp instead of dbcp2.
+ - Use collections instead of collections4.
+ - Use lang instead of lang3.
+ - Use pool instead of pool2.
+ - and so on...
+ -->
+ <commons.componentid>${project.artifactId}</commons.componentid>
+
+ <!-- The package id is substring of the package name from o.a.commons.(.*)., for example:
+ - Use dbcp2 instead of dbcp.
+ - Use collections4 instead of collections.
+ - Use lang3 instead of lang.
+ - Use pool2 instead of pool.
+ - and so on...
+ -->
+ <commons.packageId>${project.artifactId}</commons.packageId>
+
+ <!-- Configuration properties for the OSGi maven-bundle-plugin -->
+ <commons.osgi.symbolicName>org.apache.commons.${commons.packageId}</commons.osgi.symbolicName>
+ <commons.osgi.export>org.apache.commons.*;version=${project.version};-noimport:=true</commons.osgi.export>
+ <commons.osgi.import>*</commons.osgi.import>
+ <commons.osgi.dynamicImport />
+ <commons.osgi.private />
+ <commons.osgi.excludeDependencies>true</commons.osgi.excludeDependencies>
+
+ <!-- location of any manifest file used by maven-jar-plugin -->
+ <commons.manifestfile>${project.build.directory}/osgi/MANIFEST.MF</commons.manifestfile>
+
+ <!--
+ Make the deployment protocol pluggable. This allows to switch to
+ other protocols like scpexe, which some users prefer over scp.
+ -->
+ <commons.deployment.protocol>scp</commons.deployment.protocol>
+
+ <!--
+ Encoding of Java source files: ensures that the compiler and
+ the javadoc generator use the right encoding. Subprojects may
+ overwrite this, if they are using another encoding.
+ -->
+ <commons.encoding>iso-8859-1</commons.encoding>
+ <!-- used in this pom to provide the Javadoc HTML file encoding -->
+ <commons.docEncoding>${commons.encoding}</commons.docEncoding>
+ <!-- Define source encoding for filtering; used by general plugins -->
+ <project.build.sourceEncoding>${commons.encoding}</project.build.sourceEncoding>
+ <!-- This is used by reporting plugins -->
+ <project.reporting.outputEncoding>${commons.encoding}</project.reporting.outputEncoding>
+
+ <!-- Javadoc link to Java API. Default is Java 1.7; components can override to other versions -->
+ <commons.javadoc6.java.link>http://docs.oracle.com/javase/6/docs/api/</commons.javadoc6.java.link>
+ <commons.javadoc7.java.link>http://docs.oracle.com/javase/7/docs/api/</commons.javadoc7.java.link>
+ <commons.javadoc8.java.link>http://docs.oracle.com/javase/8/docs/api/</commons.javadoc8.java.link>
+ <commons.javadoc9.java.link>http://docs.oracle.com/javase/9/docs/api/</commons.javadoc9.java.link>
+ <commons.javadoc10.java.link>http://docs.oracle.com/javase/10/docs/api/</commons.javadoc10.java.link>
+ <commons.javadoc11.java.link>https://docs.oracle.com/en/java/javase/11/docs/api/</commons.javadoc11.java.link>
+ <commons.javadoc12.java.link>https://docs.oracle.com/en/java/javase/12/docs/api/</commons.javadoc12.java.link>
+
+ <commons.javadoc.java.link>${commons.javadoc7.java.link}</commons.javadoc.java.link>
+
+ <commons.javadoc.javaee5.link>http://docs.oracle.com/javaee/5/api/</commons.javadoc.javaee5.link>
+ <commons.javadoc.javaee6.link>http://docs.oracle.com/javaee/6/api/</commons.javadoc.javaee6.link>
+ <commons.javadoc.javaee7.link>http://docs.oracle.com/javaee/7/api/</commons.javadoc.javaee7.link>
+
+ <commons.javadoc.javaee.link>${commons.javadoc.javaee6.link}</commons.javadoc.javaee.link>
+
+ <!-- build meta inf -->
+ <maven.build.timestamp.format>yyyy-MM-dd HH:mm:ssZ</maven.build.timestamp.format>
+ <implementation.build>${scmBranch}@r${buildNumber}; ${maven.build.timestamp}</implementation.build>
+
+ <!-- Allow Clirr severity to be overriden by the command-line option -DminSeverity=level -->
+ <minSeverity>info</minSeverity>
+
+ <!-- Control number of issues retrieved from JIRA with changes plugin -->
+ <commons.changes.maxEntries>100</commons.changes.maxEntries>
+
+ <!-- Allow surefire-report aggregation to be easily configured for multi-module projects -->
+ <commons.surefire-report.aggregate>false</commons.surefire-report.aggregate>
+
+ <!-- Allow changes Jira report to be restricted to just the current version (plugin default is false) -->
+ <commons.changes.onlyCurrentVersion>false</commons.changes.onlyCurrentVersion>
+ <!-- Allow changes Jira report maxEntries to be overridden (plugin default 100) -->
+ <commons.changes.maxEntries>100</commons.changes.maxEntries>
+ <!-- Allow changes Jira report runOnlyAtExecutionRoot to be overridden (plugin default is false) -->
+ <commons.changes.runOnlyAtExecutionRoot>false</commons.changes.runOnlyAtExecutionRoot>
+
+ <!-- scm publish plugin configuration -->
+ <commons.site.cache>${user.home}/commons-sites</commons.site.cache>
+ <!-- value modules can override it -->
+ <commons.site.path>${commons.componentid}</commons.site.path>
+
+ <commons.scmPubUrl>https://svn.apache.org/repos/infra/websites/production/commons/content/proper/commons-${commons.componentid}</commons.scmPubUrl>
+ <commons.scmPubCheckoutDirectory>${commons.site.cache}/${commons.site.path}</commons.scmPubCheckoutDirectory>
+ <commons.scmPubServer>commons.site</commons.scmPubServer>
+
+ <!-- allow japicmp's breakBuildOnBinaryIncompatibleModifications
+ to be overridden, plugin's default is false -->
+ <commons.japicmp.breakBuildOnBinaryIncompatibleModifications>true</commons.japicmp.breakBuildOnBinaryIncompatibleModifications>
+ <commons.japicmp.breakBuildOnSourceIncompatibleModifications>false</commons.japicmp.breakBuildOnSourceIncompatibleModifications>
+ <commons.japicmp.ignoreMissingClasses>false</commons.japicmp.ignoreMissingClasses>
+ <!-- disable japicmp by default -->
+ <japicmp.skip>true</japicmp.skip>
+
+ <!-- Commons Release plugin: dist dev site -->
+ <commons.distSvnStagingUrl>scm:svn:https://dist.apache.org/repos/dist/dev/commons/${commons.componentid}</commons.distSvnStagingUrl>
+
+ <!-- Commons Release plugin: release manager -->
+ <commons.releaseManagerName>${user.name}</commons.releaseManagerName>
+ <commons.releaseManagerKey>DEADBEEF</commons.releaseManagerKey>
+
+ <sonar.host.url>https://analysis.apache.org/</sonar.host.url>
+
+ </properties>
<mailingLists>
<!-- N.B. commons-site now uses the Apache POM so has its own copy of the mailing list definitions -->
@@ -166,6 +373,31 @@
</otherArchives>
</mailingList>
</mailingLists>
+
+ <prerequisites>
+ <maven>3.0.5</maven>
+ </prerequisites>
+
+ <!--
+ This section *must* be overwritten by subprojects. It is only to allow
+ a release of the commons-parent POM.
+ -->
+ <scm>
+ <connection>scm:git:http://gitbox.apache.org/repos/asf/commons-parent.git</connection>
+ <developerConnection>scm:git:https://gitbox.apache.org/repos/asf/commons-parent.git</developerConnection>
+ <url>https://gitbox.apache.org/repos/asf?p=commons-parent.git</url>
+ </scm>
+
+ <issueManagement>
+ <system>jira</system>
+ <url>https://issues.apache.org/jira/browse/COMMONSSITE</url>
+ </issueManagement>
+
+ <ciManagement>
+ <system>jenkins</system>
+ <url>https://builds.apache.org/</url>
+ </ciManagement>
+
<build>
<!-- TODO find a better way to add N&L files to jars and test jars
See also maven-remote-resources-plugin configuration below.
@@ -1629,233 +1861,4 @@
</profiles>
- <properties>
- <!-- configuration bits for cutting a release candidate, must be overridden by components -->
- <commons.release.version>${project.version}</commons.release.version>
- <commons.rc.version>RC1</commons.rc.version>
- <commons.jira.id>COMMONSSITE</commons.jira.id>
-
- <!-- Default configuration for compiler source and target JVM -->
- <!-- Do NOT change this; it must remain as 1.3 -->
- <!--
- It's important that child POMs don't need to change when the parent POM is updated.
- At the time when these properties were introduced, the default Java version was 1.3.
- Thus components that failed to define the version would not be affected by updates
- to the Commons Parent or its parent the Apache pom.
- Of course most if not all components now define the properties.
- However it's still important to keep the properties as they effectively
- force child poms to define the Java version they require.
- -->
- <maven.compiler.source>1.3</maven.compiler.source>
- <maven.compiler.target>1.3</maven.compiler.target>
-
- <!-- compiler and surefire plugin settings for "java" profiles -->
- <commons.compiler.fork>false</commons.compiler.fork>
- <commons.compiler.compilerVersion />
- <commons.compiler.javac />
-
- <!-- plugin versions (allows same value in reporting and build sections; also allows easy override) -->
- <commons.build-plugin.version>1.10</commons.build-plugin.version>
- <commons.release-plugin.version>1.6</commons.release-plugin.version>
- <commons.surefire.version>2.22.2</commons.surefire.version>
- <commons.failsafe.version>2.22.2</commons.failsafe.version>
- <commons.surefire-report.version>2.22.2</commons.surefire-report.version>
- <commons.javadoc.version>3.1.1</commons.javadoc.version>
- <commons.rat.version>0.13</commons.rat.version>
- <commons.changes.version>2.12.1</commons.changes.version>
- <commons.clirr.version>2.8</commons.clirr.version>
- <commons.japicmp.version>0.14.1</commons.japicmp.version>
- <commons.jxr.version>3.0.0</commons.jxr.version>
- <commons.project-info.version>3.0.0</commons.project-info.version>
- <commons.wagon-ssh.version>3.3.3</commons.wagon-ssh.version>
- <!--
- Note: Maven site plugin 3.5.1 is the latest version but is not a direct replacement:
-
- https://maven.apache.org/plugins/maven-site-plugin/migrate.html
-
- In particular, adding CDATA to header and footer sections is not backwards compatible.
- I.e. these have to be updated at the same time.
-
- Also it causes the following errors:
-
- [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.5.1:site (default-site) on project commons-parent:
- Execution default-site of goal org.apache.maven.plugins:maven-site-plugin:3.5.1:site failed:
- A required class was missing while executing org.apache.maven.plugins:maven-site-plugin:3.5.1:site: org/apache/maven/doxia/sink/impl/XhtmlBaseSink
-
- This is because Apache POM 17 forces an older version of Doxia core:
- https://mail-archives.apache.org/mod_mbox/maven-users/201602.mbox/%3C2337255.xU7aS9G1qr@herve-desktop%3E
-
- The same error applies when running with version 3.5.
-
- Since the version is defined as a property, the CP version can be overridden as follows if necessary:
-
- mvn site -Dcommons.site-plugin.version=3.5.1
-
- You will also need to add a dependency on Doxia core:
- <artifactId>maven-site-plugin</artifactId>
- <dependencies>
- <dependency>
- <groupId>org.apache.maven.doxia</groupId>
- <artifactId>doxia-core</artifactId>
- <version>1.8</version>
- </dependency>
- </dependencies>
-
- -->
- <commons.source-plugin.version>3.1.0</commons.source-plugin.version>
- <commons.checkstyle-plugin.version>3.1.0</commons.checkstyle-plugin.version>
- <commons.jar-plugin.version>3.1.2</commons.jar-plugin.version>
- <commons.assembly-plugin.version>3.1.1</commons.assembly-plugin.version>
- <commons.site-plugin.version>3.7.1</commons.site-plugin.version>
- <commons.jacoco.version>0.8.3</commons.jacoco.version>
- <commons.cobertura.version>2.7</commons.cobertura.version>
- <commons.coveralls.version>4.3.0</commons.coveralls.version>
- <commons.coveralls.timestampFormat>EpochMillis</commons.coveralls.timestampFormat>
- <commons.jdepend.version>2.0</commons.jdepend.version>
- <commons.compiler.version>3.8.1</commons.compiler.version>
- <commons.scm-publish.version>1.1</commons.scm-publish.version>
- <commons.findbugs.version>3.0.5</commons.findbugs.version>
- <commons.spotbugs.version>3.1.6</commons.spotbugs.version>
- <commons.pmd.version>3.12.0</commons.pmd.version>
- <commons.felix.version>4.2.0</commons.felix.version>
- <commons.build-helper.version>3.0.0</commons.build-helper.version>
- <commons.animal-sniffer.version>1.17</commons.animal-sniffer.version>
- <!-- Almost all signatures use version 1.0. Allow override just in case -->
- <commons.animal-sniffer.signature.version>1.0</commons.animal-sniffer.signature.version>
-
- <!-- Default values for the download-page generation by commons-build-plugin -->
- <commons.release.name>${project.artifactId}-${commons.release.version}</commons.release.name>
- <commons.release.desc />
- <commons.binary.suffix>-bin</commons.binary.suffix>
- <commons.release.2.name>${project.artifactId}-${commons.release.2.version}</commons.release.2.name>
- <commons.release.2.desc />
- <commons.release.2.binary.suffix>-bin</commons.release.2.binary.suffix>
- <commons.release.3.name>${project.artifactId}-${commons.release.3.version}</commons.release.3.name>
- <commons.release.3.desc />
- <commons.release.3.binary.suffix>-bin</commons.release.3.binary.suffix>
- <commons.release.4.desc />
- <commons.release.4.binary.suffix>-bin</commons.release.4.binary.suffix>
-
- <!-- Default values for the jacoco-maven-plugin reports -->
- <commons.jacoco.classRatio>1.00</commons.jacoco.classRatio>
- <commons.jacoco.instructionRatio>0.90</commons.jacoco.instructionRatio>
- <commons.jacoco.methodRatio>0.95</commons.jacoco.methodRatio>
- <commons.jacoco.branchRatio>0.85</commons.jacoco.branchRatio>
- <commons.jacoco.complexityRatio>0.85</commons.jacoco.complexityRatio>
- <commons.jacoco.lineRatio>0.90</commons.jacoco.lineRatio>
- <commons.jacoco.haltOnFailure>false</commons.jacoco.haltOnFailure>
-
- <!-- The Commons component id is used on the distribution server, for example:
- - Use dbcp instead of dbcp2.
- - Use collections instead of collections4.
- - Use lang instead of lang3.
- - Use pool instead of pool2.
- - and so on...
- -->
- <commons.componentid>${project.artifactId}</commons.componentid>
-
- <!-- The package id is substring of the package name from o.a.commons.(.*)., for example:
- - Use dbcp2 instead of dbcp.
- - Use collections4 instead of collections.
- - Use lang3 instead of lang.
- - Use pool2 instead of pool.
- - and so on...
- -->
- <commons.packageId>${project.artifactId}</commons.packageId>
-
- <!-- Configuration properties for the OSGi maven-bundle-plugin -->
- <commons.osgi.symbolicName>org.apache.commons.${commons.packageId}</commons.osgi.symbolicName>
- <commons.osgi.export>org.apache.commons.*;version=${project.version};-noimport:=true</commons.osgi.export>
- <commons.osgi.import>*</commons.osgi.import>
- <commons.osgi.dynamicImport />
- <commons.osgi.private />
- <commons.osgi.excludeDependencies>true</commons.osgi.excludeDependencies>
-
- <!-- location of any manifest file used by maven-jar-plugin -->
- <commons.manifestfile>${project.build.directory}/osgi/MANIFEST.MF</commons.manifestfile>
-
- <!--
- Make the deployment protocol pluggable. This allows to switch to
- other protocols like scpexe, which some users prefer over scp.
- -->
- <commons.deployment.protocol>scp</commons.deployment.protocol>
-
- <!--
- Encoding of Java source files: ensures that the compiler and
- the javadoc generator use the right encoding. Subprojects may
- overwrite this, if they are using another encoding.
- -->
- <commons.encoding>iso-8859-1</commons.encoding>
- <!-- used in this pom to provide the Javadoc HTML file encoding -->
- <commons.docEncoding>${commons.encoding}</commons.docEncoding>
- <!-- Define source encoding for filtering; used by general plugins -->
- <project.build.sourceEncoding>${commons.encoding}</project.build.sourceEncoding>
- <!-- This is used by reporting plugins -->
- <project.reporting.outputEncoding>${commons.encoding}</project.reporting.outputEncoding>
-
- <!-- Javadoc link to Java API. Default is Java 1.7; components can override to other versions -->
- <commons.javadoc6.java.link>http://docs.oracle.com/javase/6/docs/api/</commons.javadoc6.java.link>
- <commons.javadoc7.java.link>http://docs.oracle.com/javase/7/docs/api/</commons.javadoc7.java.link>
- <commons.javadoc8.java.link>http://docs.oracle.com/javase/8/docs/api/</commons.javadoc8.java.link>
- <commons.javadoc9.java.link>http://docs.oracle.com/javase/9/docs/api/</commons.javadoc9.java.link>
- <commons.javadoc10.java.link>http://docs.oracle.com/javase/10/docs/api/</commons.javadoc10.java.link>
- <commons.javadoc11.java.link>https://docs.oracle.com/en/java/javase/11/docs/api/</commons.javadoc11.java.link>
- <commons.javadoc12.java.link>https://docs.oracle.com/en/java/javase/12/docs/api/</commons.javadoc12.java.link>
-
- <commons.javadoc.java.link>${commons.javadoc7.java.link}</commons.javadoc.java.link>
-
- <commons.javadoc.javaee5.link>http://docs.oracle.com/javaee/5/api/</commons.javadoc.javaee5.link>
- <commons.javadoc.javaee6.link>http://docs.oracle.com/javaee/6/api/</commons.javadoc.javaee6.link>
- <commons.javadoc.javaee7.link>http://docs.oracle.com/javaee/7/api/</commons.javadoc.javaee7.link>
-
- <commons.javadoc.javaee.link>${commons.javadoc.javaee6.link}</commons.javadoc.javaee.link>
-
- <!-- build meta inf -->
- <maven.build.timestamp.format>yyyy-MM-dd HH:mm:ssZ</maven.build.timestamp.format>
- <implementation.build>${scmBranch}@r${buildNumber}; ${maven.build.timestamp}</implementation.build>
-
- <!-- Allow Clirr severity to be overriden by the command-line option -DminSeverity=level -->
- <minSeverity>info</minSeverity>
-
- <!-- Control number of issues retrieved from JIRA with changes plugin -->
- <commons.changes.maxEntries>100</commons.changes.maxEntries>
-
- <!-- Allow surefire-report aggregation to be easily configured for multi-module projects -->
- <commons.surefire-report.aggregate>false</commons.surefire-report.aggregate>
-
- <!-- Allow changes Jira report to be restricted to just the current version (plugin default is false) -->
- <commons.changes.onlyCurrentVersion>false</commons.changes.onlyCurrentVersion>
- <!-- Allow changes Jira report maxEntries to be overridden (plugin default 100) -->
- <commons.changes.maxEntries>100</commons.changes.maxEntries>
- <!-- Allow changes Jira report runOnlyAtExecutionRoot to be overridden (plugin default is false) -->
- <commons.changes.runOnlyAtExecutionRoot>false</commons.changes.runOnlyAtExecutionRoot>
-
- <!-- scm publish plugin configuration -->
- <commons.site.cache>${user.home}/commons-sites</commons.site.cache>
- <!-- value modules can override it -->
- <commons.site.path>${commons.componentid}</commons.site.path>
-
- <commons.scmPubUrl>https://svn.apache.org/repos/infra/websites/production/commons/content/proper/commons-${commons.componentid}</commons.scmPubUrl>
- <commons.scmPubCheckoutDirectory>${commons.site.cache}/${commons.site.path}</commons.scmPubCheckoutDirectory>
- <commons.scmPubServer>commons.site</commons.scmPubServer>
-
- <!-- allow japicmp's breakBuildOnBinaryIncompatibleModifications
- to be overridden, plugin's default is false -->
- <commons.japicmp.breakBuildOnBinaryIncompatibleModifications>true</commons.japicmp.breakBuildOnBinaryIncompatibleModifications>
- <commons.japicmp.breakBuildOnSourceIncompatibleModifications>false</commons.japicmp.breakBuildOnSourceIncompatibleModifications>
- <commons.japicmp.ignoreMissingClasses>false</commons.japicmp.ignoreMissingClasses>
- <!-- disable japicmp by default -->
- <japicmp.skip>true</japicmp.skip>
-
- <!-- Commons Release plugin: dist dev site -->
- <commons.distSvnStagingUrl>scm:svn:https://dist.apache.org/repos/dist/dev/commons/${commons.componentid}</commons.distSvnStagingUrl>
-
- <!-- Commons Release plugin: release manager -->
- <commons.releaseManagerName>${user.name}</commons.releaseManagerName>
- <commons.releaseManagerKey>DEADBEEF</commons.releaseManagerKey>
-
- <sonar.host.url>https://analysis.apache.org/</sonar.host.url>
-
- </properties>
-
</project>