This is an automated email from the ASF dual-hosted git repository.
ggregory pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-crypto.git
The following commit(s) were added to refs/heads/master by this push:
new 4454014 Prepare for 1.1.0 RC1.
4454014 is described below
commit 4454014ca82cc5ed14fb01ca812d71637295d1a1
Author: Gary Gregory <[email protected]>
AuthorDate: Thu Aug 27 19:51:41 2020 -0400
Prepare for 1.1.0 RC1.
---
CONTRIBUTING.md | 44 +++++++++++++------
README.md | 24 ++++++-----
RELEASE-NOTES.txt | 89 +++++++++++++++++++++++++++++++++++++++
pom.xml | 4 +-
src/changes/changes.xml | 2 +
src/site/xdoc/download_crypto.xml | 46 ++++++++++----------
src/site/xdoc/issue-tracking.xml | 4 +-
src/site/xdoc/mail-lists.xml | 30 ++++++-------
8 files changed, 178 insertions(+), 65 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 27dc860..3a5e3e0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -25,7 +25,7 @@
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:contributing-md |
+ | 1) Re-generate using: mvn commons-build:contributing-md |
| |
| 2) Set the following properties in the component's pom: |
| - commons.jira.id (required, alphabetic, upper case) |
@@ -51,47 +51,65 @@ Getting Started
+ Make sure you have a [JIRA account](https://issues.apache.org/jira/).
+ Make sure you have a [GitHub account](https://github.com/signup/free).
+ If you're planning to implement a new feature it makes sense to discuss your
changes on the [dev list](https://commons.apache.org/mail-lists.html) first.
This way you can make sure you're not wasting your time on something that isn't
considered to be in Apache Commons Crypto's scope.
-+ Submit a ticket for your issue, assuming one does not already exist.
++ Submit a [Jira Ticket][jira] for your issue, assuming one does not already
exist.
+ Clearly describe the issue including steps to reproduce when it is a bug.
+ Make sure you fill in the earliest version that you know has the issue.
-+ Fork the repository on GitHub.
++ Find the corresponding [repository on
GitHub](https://github.com/apache/?query=commons-),
+[fork](https://help.github.com/articles/fork-a-repo/) and check out your
forked repository.
Making Changes
--------------
-+ Create a topic branch from where you want to base your work (this is usually
the master/trunk branch).
++ Create a _topic branch_ for your isolated work.
+ * Usually you should base your branch on the `master` or `trunk` branch.
+ * A good topic branch name can be the JIRA bug id plus a keyword, e.g.
`CRYPTO-123-InputStream`.
+ * If you have submitted multiple JIRA issues, try to maintain separate
branches and pull requests.
+ Make commits of logical units.
+ * Make sure your commit messages are meaningful and in the proper format.
Your commit message should contain the key of the JIRA issue.
+ * e.g. `CRYPTO-123: Close input stream earlier`
+ Respect the original code style:
+ Only use spaces for indentation.
- + Create minimal diffs - disable on save actions like reformat source code
or organize imports. If you feel the source code should be reformatted create a
separate PR for this change.
- + Check for unnecessary whitespace with git diff --check before committing.
-+ Make sure your commit messages are in the proper format. Your commit message
should contain the key of the JIRA issue.
-+ Make sure you have added the necessary tests for your changes.
+ + Create minimal diffs - disable _On Save_ actions like _Reformat Source
Code_ or _Organize Imports_. If you feel the source code should be reformatted
create a separate PR for this change first.
+ + Check for unnecessary whitespace with `git diff` -- check before
committing.
++ Make sure you have added the necessary tests for your changes, typically in
`src/test/java`.
+ Run all the tests with `mvn clean verify` to assure nothing else was
accidentally broken.
Making Trivial Changes
----------------------
+The JIRA tickets are used to generate the changelog for the next release.
+
For changes of a trivial nature to comments and documentation, it is not
always necessary to create a new ticket in JIRA.
In this case, it is appropriate to start the first line of a commit with
'(doc)' instead of a ticket number.
+
Submitting Changes
------------------
-+ Sign the [Contributor License Agreement][cla] if you haven't already.
++ Sign and submit the Apache [Contributor License Agreement][cla] if you
haven't already.
+ * Note that small patches & typical bug fixes do not require a CLA as
+ clause 5 of the [Apache
License](https://www.apache.org/licenses/LICENSE-2.0.html#contributions)
+ covers them.
+ Push your changes to a topic branch in your fork of the repository.
-+ Submit a pull request to the repository in the apache organization.
++ Submit a _Pull Request_ to the corresponding repository in the `apache`
organization.
+ * Verify _Files Changed_ shows only your intended changes and does not
+ include additional files like `target/*.class`
+ Update your JIRA ticket and include a link to the pull request in the ticket.
+If you prefer to not use GitHub, then you can instead use
+`git format-patch` (or `svn diff`) and attach the patch file to the JIRA issue.
+
+
Additional Resources
--------------------
+ [Contributing patches](https://commons.apache.org/patches.html)
-+ [Apache Commons Crypto JIRA project
page](https://issues.apache.org/jira/browse/CRYPTO)
++ [Apache Commons Crypto JIRA project page][jira]
+ [Contributor License Agreement][cla]
+ [General GitHub documentation](https://help.github.com/)
-+ [GitHub pull request
documentation](https://help.github.com/send-pull-requests/)
++ [GitHub pull request
documentation](https://help.github.com/articles/creating-a-pull-request/)
+ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons)
-+ #apachecommons IRC channel on freenode.org
++ `#apache-commons` IRC channel on `irc.freenode.net`
[cla]:https://www.apache.org/licenses/#clas
+[jira]:https://issues.apache.org/jira/browse/CRYPTO
diff --git a/README.md b/README.md
index 2fb3dd1..2222c5a 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:readme-md |
+ | 1) Re-generate using: mvn commons-build:readme-md |
| |
| 2) Set the following properties in the component's pom: |
| - commons.componentid (required, alphabetic, lower case) |
@@ -43,10 +43,10 @@
Apache Commons Crypto
===================
-[](https://travis-ci.org/apache/commons-crypto)
-[](https://coveralls.io/github/apache/commons-crypto?branch=master)
+[](https://travis-ci.org/apache/commons-crypto)
+[](https://coveralls.io/r/apache/commons-crypto)
[](https://maven-badges.herokuapp.com/maven-central/org.apache.commons/commons-crypto/)
-[](http://www.apache.org/licenses/LICENSE-2.0.html)
+[](https://javadoc.io/doc/org.apache.commons/commons-crypto/1.1.0)
Apache Commons Crypto is a cryptographic library optimized with AES-NI
(Advanced Encryption
Standard New Instructions). It provides Java API for both cipher level and
Java stream level.
@@ -96,8 +96,8 @@ The following provides more details on the included
cryptographic software:
Documentation
-------------
-More information can be found on the
[homepage](https://commons.apache.org/proper/commons-crypto).
-The
[Javadoc](https://commons.apache.org/proper/commons-crypto/javadocs/api-release)
can be browsed.
+More information can be found on the [Apache Commons Crypto
homepage](https://commons.apache.org/proper/commons-crypto).
+The [Javadoc](https://commons.apache.org/proper/commons-crypto/apidocs) can be
browsed.
Questions related to the usage of Apache Commons Crypto should be posted to
the [user mailing list][ml].
Where can I get the latest release?
@@ -110,14 +110,14 @@ Alternatively you can pull it from the central Maven
repositories:
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-crypto</artifactId>
- <version>1.0.0</version>
+ <version>1.1.0</version>
</dependency>
```
Contributing
------------
-We accept PRs via github. The [developer mailing list][ml] is the main channel
of communication for contributors.
+We accept Pull Requests via GitHub. The [developer mailing list][ml] is the
main channel of communication for contributors.
There are some guidelines which will make applying PRs easier for us:
+ No tabs! Please use spaces for indentation.
+ Respect the code style.
@@ -129,7 +129,9 @@ You can learn more about contributing via GitHub in our
[contribution guidelines
License
-------
-Code is under the [Apache Licence
v2](https://www.apache.org/licenses/LICENSE-2.0.txt).
+This code is under the [Apache Licence
v2](https://www.apache.org/licenses/LICENSE-2.0).
+
+See the `NOTICE.txt` file for required notices and attributions.
Donations
---------
@@ -139,8 +141,8 @@ Additional Resources
--------------------
+ [Apache Commons Homepage](https://commons.apache.org/)
-+ [Apache Bugtracker (JIRA)](https://issues.apache.org/jira/)
++ [Apache Issue Tracker (JIRA)](https://issues.apache.org/jira/browse/CRYPTO)
+ [Apache Commons Twitter Account](https://twitter.com/ApacheCommons)
-+ #apachecommons IRC channel on freenode.org
++ `#apache-commons` IRC channel on `irc.freenode.org`
[ml]:https://commons.apache.org/mail-lists.html
diff --git a/RELEASE-NOTES.txt b/RELEASE-NOTES.txt
index 7529ae1..56d635a 100644
--- a/RELEASE-NOTES.txt
+++ b/RELEASE-NOTES.txt
@@ -1,3 +1,92 @@
+ Apache Commons Crypto 1.1.0
+ RELEASE NOTES
+
+The Apache Commons Crypto team is pleased to announce the release of Apache
Commons Crypto 1.1.0
+
+Apache Commons Crypto is a cryptographic library optimized with AES-NI
(Advanced Encryption
+Standard New Instructions). It provides Java API for both cipher level and
Java stream level.
+Developers can use it to implement high performance AES encryption/decryption
with the minimum
+code and effort. Please note that Crypto doesn't implement the cryptographic
algorithm such as
+AES directly. It wraps to Openssl or JCE which implement the algorithms.
+
+Features
+--------
+
+1. Cipher API for low level cryptographic operations.
+2. Java stream API (CryptoInputStream/CryptoOutputStream) for high level
stream encryption/decryption.
+3. Both optimized with high performance AES encryption/decryption. (1400 MB/s
- 1700 MB/s throughput in modern Xeon processors).
+4. JNI-based implementation to achieve comparable performance to the native
C/C++ version based on OpenSsl.
+5. Portable across various operating systems (currently only
Linux/MacOSX/Windows);
+Apache Commons Crypto loads the library according to your machine environment
(it checks system properties, `os.name` and `os.arch`).
+6. Simple usage. Add the commons-crypto-(version).jar file to your classpath.
+
+
+Export restrictions
+-------------------
+
+This distribution includes cryptographic software.
+The country in which you currently reside may have restrictions
+on the import, possession, use, and/or re-export to another country,
+of encryption software. BEFORE using any encryption software,
+please check your country's laws, regulations and policies
+concerning the import, possession, or use, and re-export of
+encryption software, to see if this is permitted.
+See <http://www.wassenaar.org/> for more information.
+
+The U.S. Government Department of Commerce, Bureau of Industry and Security
(BIS),
+has classified this software as Export Commodity Control Number (ECCN)
5D002.C.1,
+which includes information security software using or performing
+cryptographic functions with asymmetric algorithms.
+The form and manner of this Apache Software Foundation distribution makes
+it eligible for export under the License Exception
+ENC Technology Software Unrestricted (TSU) exception
+(see the BIS Export Administration Regulations, Section 740.13)
+for both object code and source code.
+
+The following provides more details on the included cryptographic software:
+
+* Commons Crypto use [Java Cryptography
Extension](http://docs.oracle.com/javase/8/docs/technotes/guides/security/crypto/CryptoSpec.html)
provided by Java
+* Commons Crypto link to and use [OpenSSL](https://www.openssl.org/) ciphers
+
+Minor release (Java 8 and OpenSSL 1.1.1)
+
+Changes in this version include:
+
+New features:
+o CRYPTO-59: Support Galois/Counter Mode (GCM).
+o CRYPTO-131: Provide FAQ page.
+o CRYPTO-139: Add support for AARCH64.
+o CRYPTO-139: Make org.apache.commons.crypto.stream.input.Input extend
Closeable.
+o CRYPTO-139: Make org.apache.commons.crypto.stream.output.Output extend
Closeable.
+
+Fixed Bugs:
+o CRYPTO-125: CryptoOutputStream does not call write in a loop when
underlying channel works in non-block mode.
+o CRYPTO-134: CipherByteBufferExample should not truncate the string
+o CRYPTO-137: Error compiling on Win64 with Mingw.
+o CRYPTO-138: CipherByteArrayExample fails on OpenSSL 1.1.0g with
java.lang.UnsatisfiedLinkError: EVP_CIPHER_CTX_cleanup.
+o CRYPTO-141: Errors in native code can leave Java wrappers in bad state.
+o CRYPTO-141: Intermittent Failure in GCMCipherTest#testGcmTamperedData()
#105. Thanks to Alex Remily.
+
+Changes:
+o Add support for ARM.
+o Add support for ARM-HF.
+o Reset JAVA_HOME for aarch64 and ppc builds. Turn off
maven-enforcer for Xenial builds #104. Thanks to Geoffrey Blake.
+o Update maven-checkstyle-plugin 3.0.0 -> 3.1.1.
+o Update commons-parent 51 -> 52.
+o Update maven-resources-plugin 3.1.0 -> 3.2.0.
+o Update Apache CLIRR to JApiCmp.
+o Update FindBugs to SpotBugs.
+
+
+Historical list of changes:
https://commons.apache.org/proper/commons-crypto/changes-report.html
+
+For complete information on Apache Commons Crypto, including instructions on
how to submit bug reports,
+patches, or suggestions for improvement, see the Apache Apache Commons Crypto
website:
+
+https://commons.apache.org/proper/commons-crypto/
+
+-----------------------------------------------------------------------------
+
Apache Commons Crypto 1.0.0
RELEASE NOTES
diff --git a/pom.xml b/pom.xml
index ffb02af..c16d1f5 100644
--- a/pom.xml
+++ b/pom.xml
@@ -80,7 +80,7 @@ The following provides more details on the included
cryptographic software:
<licenses>
<license>
<name>Apache License, Version 2.0</name>
- <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
+ <url>https://www.apache.org/licenses/LICENSE-2.0.txt</url>
</license>
</licenses>
@@ -104,7 +104,7 @@ The following provides more details on the included
cryptographic software:
<distributionManagement>
<site>
<id>commons.site</id>
- <name>Apache Commons Site SVN</name>
+ <name>Apache Commons Site</name>
<url>scm:svn:${commons.scmPubUrl}</url>
</site>
</distributionManagement>
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index c648d9a..ed58ce9 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -73,6 +73,8 @@
<action issue="CRYPTO-141" type="fix" dev="ggregory" due-to="Alex
Remily">Intermittent Failure in GCMCipherTest#testGcmTamperedData()
#105.</action>
<action issue="CRYPTO-139" type="add">Make
org.apache.commons.crypto.stream.input.Input extend Closeable.</action>
<action issue="CRYPTO-139" type="add">Make
org.apache.commons.crypto.stream.output.Output extend Closeable.</action>
+ <action type="update" dev="ggregory">Add support for
ARM.</action>
+ <action type="update" dev="ggregory">Add support for
ARM-HF.</action>
<action type="update" dev="ggregory" due-to="Geoffrey
Blake">Reset JAVA_HOME for aarch64 and ppc builds. Turn off maven-enforcer for
Xenial builds #104.</action>
<action type="update" dev="ggregory">Update
maven-checkstyle-plugin 3.0.0 -> 3.1.1.</action>
<action type="update" dev="ggregory">Update
commons-parent 51 -> 52.</action>
diff --git a/src/site/xdoc/download_crypto.xml
b/src/site/xdoc/download_crypto.xml
index 36d2f1e..f5bdd8f 100644
--- a/src/site/xdoc/download_crypto.xml
+++ b/src/site/xdoc/download_crypto.xml
@@ -26,22 +26,24 @@ limitations under the License.
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:download-page |
+ | 1) Re-generate using: mvn commons-build:download-page |
| |
| 2) Set the following properties in the component's pom: |
- | - commons.componentid (required, alphabetic, lower case) |
+ | - commons.componentid (required, alphabetic, lower case) |
| - commons.release.version (required) |
| - commons.release.name (required) |
| - commons.binary.suffix (optional) |
| (defaults to "-bin", set to "" for pre-maven2 releases) |
| - commons.release.desc (optional) |
| - commons.release.subdir (optional) |
+ | - commons.release.hash (optional, lowercase, default sha512) |
| |
- | - commons.release.2/3.version (conditional) |
- | - commons.release.2/3.name (conditional) |
- | - commons.release.2/3.binary.suffix (optional) |
- | - commons.release.2/3.desc (optional) |
- | - commons.release.2/3.subdir (optional) |
+ | - commons.release.[234].version (conditional) |
+ | - commons.release.[234].name (conditional) |
+ | - commons.release.[234].binary.suffix (optional) |
+ | - commons.release.[234].desc (optional) |
+ | - commons.release.[234].subdir (optional) |
+ | - commons.release.[234].hash (optional, lowercase, [sha512])|
| |
| 3) Example Properties |
| (commons.release.name inherited by parent: |
@@ -64,7 +66,7 @@ limitations under the License.
<subsection name="Using a Mirror">
<p>
We recommend you use a mirror to download our release
- builds, but you <strong>must</strong> <a
href="http://www.apache.org/info/verification.html";>verify the integrity</a> of
+ builds, but you <strong>must</strong> <a
href="https://www.apache.org/info/verification.html";>verify the integrity</a> of
the downloaded files using signatures downloaded from our main
distribution directories. Recent releases (48 hours) may not yet
be available from all the mirrors.
@@ -102,7 +104,7 @@ limitations under the License.
It is essential that you
<a href="https://www.apache.org/info/verification.html";>verify the
integrity</a>
of downloaded files, preferably using the <code>PGP</code> signature
(<code>*.asc</code> files);
- failing that using the <code>MD5</code> hash (<code>*.md5</code>
checksum files).
+ failing that using the <code>SHA512</code> hash (<code>*.sha512</code>
checksum files).
</p>
<p>
The <a href="https://www.apache.org/dist/commons/KEYS";>KEYS</a>
@@ -111,32 +113,32 @@ limitations under the License.
</p>
</subsection>
</section>
- <section name="Apache Commons Crypto 1.0.0 (Requires Java 1.7 or later)">
+ <section name="Apache Commons Crypto 1.1.0 (Java 8)">
<subsection name="Binaries">
<table>
<tr>
- <td><a
href="[preferred]/commons/crypto/binaries/commons-crypto-1.0.0-bin.tar.gz">commons-crypto-1.0.0-bin.tar.gz</a></td>
- <td><a
href="https://www.apache.org/dist/commons/crypto/binaries/commons-crypto-1.0.0-bin.tar.gz.md5";>md5</a></td>
- <td><a
href="https://www.apache.org/dist/commons/crypto/binaries/commons-crypto-1.0.0-bin.tar.gz.asc";>pgp</a></td>
+ <td><a
href="[preferred]/commons/crypto/binaries/commons-crypto-1.1.0-bin.tar.gz">commons-crypto-1.1.0-bin.tar.gz</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/crypto/binaries/commons-crypto-1.1.0-bin.tar.gz.sha512";>sha512</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/crypto/binaries/commons-crypto-1.1.0-bin.tar.gz.asc";>pgp</a></td>
</tr>
<tr>
- <td><a
href="[preferred]/commons/crypto/binaries/commons-crypto-1.0.0-bin.zip">commons-crypto-1.0.0-bin.zip</a></td>
- <td><a
href="https://www.apache.org/dist/commons/crypto/binaries/commons-crypto-1.0.0-bin.zip.md5";>md5</a></td>
- <td><a
href="https://www.apache.org/dist/commons/crypto/binaries/commons-crypto-1.0.0-bin.zip.asc";>pgp</a></td>
+ <td><a
href="[preferred]/commons/crypto/binaries/commons-crypto-1.1.0-bin.zip">commons-crypto-1.1.0-bin.zip</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/crypto/binaries/commons-crypto-1.1.0-bin.zip.sha512";>sha512</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/crypto/binaries/commons-crypto-1.1.0-bin.zip.asc";>pgp</a></td>
</tr>
</table>
</subsection>
<subsection name="Source">
<table>
<tr>
- <td><a
href="[preferred]/commons/crypto/source/commons-crypto-1.0.0-src.tar.gz">commons-crypto-1.0.0-src.tar.gz</a></td>
- <td><a
href="https://www.apache.org/dist/commons/crypto/source/commons-crypto-1.0.0-src.tar.gz.md5";>md5</a></td>
- <td><a
href="https://www.apache.org/dist/commons/crypto/source/commons-crypto-1.0.0-src.tar.gz.asc";>pgp</a></td>
+ <td><a
href="[preferred]/commons/crypto/source/commons-crypto-1.1.0-src.tar.gz">commons-crypto-1.1.0-src.tar.gz</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/crypto/source/commons-crypto-1.1.0-src.tar.gz.sha512";>sha512</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/crypto/source/commons-crypto-1.1.0-src.tar.gz.asc";>pgp</a></td>
</tr>
<tr>
- <td><a
href="[preferred]/commons/crypto/source/commons-crypto-1.0.0-src.zip">commons-crypto-1.0.0-src.zip</a></td>
- <td><a
href="https://www.apache.org/dist/commons/crypto/source/commons-crypto-1.0.0-src.zip.md5";>md5</a></td>
- <td><a
href="https://www.apache.org/dist/commons/crypto/source/commons-crypto-1.0.0-src.zip.asc";>pgp</a></td>
+ <td><a
href="[preferred]/commons/crypto/source/commons-crypto-1.1.0-src.zip">commons-crypto-1.1.0-src.zip</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/crypto/source/commons-crypto-1.1.0-src.zip.sha512";>sha512</a></td>
+ <td><a
href="https://www.apache.org/dist/commons/crypto/source/commons-crypto-1.1.0-src.zip.asc";>pgp</a></td>
</tr>
</table>
</subsection>
diff --git a/src/site/xdoc/issue-tracking.xml b/src/site/xdoc/issue-tracking.xml
index 6239737..b71cbbb 100644
--- a/src/site/xdoc/issue-tracking.xml
+++ b/src/site/xdoc/issue-tracking.xml
@@ -26,7 +26,7 @@ limitations under the License.
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:jira-page |
+ | 1) Re-generate using: mvn commons-build:jira-page |
| |
| 2) Set the following properties in the component's pom: |
| - commons.jira.id (required, alphabetic, upper case) |
@@ -86,7 +86,7 @@ limitations under the License.
<p>
For more information on subversion and creating patches see the
- <a href="http://www.apache.org/dev/contributors.html";>Apache
Contributors Guide</a>.
+ <a href="https://www.apache.org/dev/contributors.html";>Apache
Contributors Guide</a>.
</p>
<p>
diff --git a/src/site/xdoc/mail-lists.xml b/src/site/xdoc/mail-lists.xml
index d12859f..e7a88d5 100644
--- a/src/site/xdoc/mail-lists.xml
+++ b/src/site/xdoc/mail-lists.xml
@@ -26,7 +26,7 @@ limitations under the License.
| commons-build-plugin/trunk/src/main/resources/commons-xdoc-templates |
+======================================================================+
| |
- | 1) Re-generate using: mvn commons:mail-page |
+ | 1) Re-generate using: mvn commons-build:mail-page |
| |
| 2) Set the following properties in the component's pom: |
| - commons.componentid (required, alphabetic, lower case) |
@@ -106,9 +106,9 @@ limitations under the License.
<td><a
href="mailto:[email protected]";>Unsubscribe</a></td>
<td><a
href="mailto:[email protected]?subject=[crypto]";>Post</a></td>
<td><a
href="https://mail-archives.apache.org/mod_mbox/commons-user/";>mail-archives.apache.org</a></td>
- <td><a
href="http://markmail.org/list/org.apache.commons.users/";>markmail.org</a><br />
- <a
href="http://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a><br
/>
- <a
href="http://news.gmane.org/gmane.comp.jakarta.commons.devel";>news.gmane.org</a>
+ <td><a
href="https://markmail.org/list/org.apache.commons.users/";>markmail.org</a><br
/>
+ <a
href="https://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a><br
/>
+ <a
href="https://news.gmane.org/gmane.comp.jakarta.commons.devel";>news.gmane.org</a>
</td>
</tr>
@@ -124,9 +124,9 @@ limitations under the License.
<td><a
href="mailto:[email protected]";>Unsubscribe</a></td>
<td><a
href="mailto:[email protected]?subject=[crypto]";>Post</a></td>
<td><a
href="https://mail-archives.apache.org/mod_mbox/commons-dev/";>mail-archives.apache.org</a></td>
- <td><a
href="http://markmail.org/list/org.apache.commons.dev/";>markmail.org</a><br />
- <a
href="http://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a><br
/>
- <a
href="http://news.gmane.org/gmane.comp.jakarta.commons.devel";>news.gmane.org</a>
+ <td><a
href="https://markmail.org/list/org.apache.commons.dev/";>markmail.org</a><br />
+ <a
href="https://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a><br
/>
+ <a
href="https://news.gmane.org/gmane.comp.jakarta.commons.devel";>news.gmane.org</a>
</td>
</tr>
@@ -142,8 +142,8 @@ limitations under the License.
<td><a
href="mailto:[email protected]";>Unsubscribe</a></td>
<td><i>read only</i></td>
<td><a
href="https://mail-archives.apache.org/mod_mbox/commons-issues/";>mail-archives.apache.org</a></td>
- <td><a
href="http://markmail.org/list/org.apache.commons.issues/";>markmail.org</a><br
/>
- <a
href="http://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a>
+ <td><a
href="https://markmail.org/list/org.apache.commons.issues/";>markmail.org</a><br
/>
+ <a
href="https://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a>
</td>
</tr>
@@ -159,8 +159,8 @@ limitations under the License.
<td><a
href="mailto:[email protected]";>Unsubscribe</a></td>
<td><i>read only</i></td>
<td><a
href="https://mail-archives.apache.org/mod_mbox/commons-commits/";>mail-archives.apache.org</a></td>
- <td><a
href="http://markmail.org/list/org.apache.commons.commits/";>markmail.org</a><br
/>
- <a
href="http://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a>
+ <td><a
href="https://markmail.org/list/org.apache.commons.commits/";>markmail.org</a><br
/>
+ <a
href="https://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a>
</td>
</tr>
@@ -192,10 +192,10 @@ limitations under the License.
<td><a class="externalLink"
href="mailto:[email protected]";>Unsubscribe</a></td>
<td><i>read only</i></td>
<td><a class="externalLink"
href="https://mail-archives.apache.org/mod_mbox/www-announce/";>mail-archives.apache.org</a></td>
- <td><a class="externalLink"
href="http://markmail.org/list/org.apache.announce/";>markmail.org</a><br />
- <a class="externalLink"
href="http://old.nabble.com/Apache-News-and-Announce-f109.html";>old.nabble.com</a><br
/>
- <a class="externalLink"
href="http://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a><br
/>
- <a class="externalLink"
href="http://news.gmane.org/gmane.comp.apache.announce";>news.gmane.org</a>
+ <td><a class="externalLink"
href="https://markmail.org/list/org.apache.announce/";>markmail.org</a><br />
+ <a class="externalLink"
href="https://old.nabble.com/Apache-News-and-Announce-f109.html";>old.nabble.com</a><br
/>
+ <a class="externalLink"
href="https://www.mail-archive.com/[email protected]/";>www.mail-archive.com</a><br
/>
+ <a class="externalLink"
href="https://news.gmane.org/gmane.comp.apache.announce";>news.gmane.org</a>
</td>
</tr>
</table>
