We have fixed a few bugs and added enhancements since the release of
Apache Commons Text 1.14.0, so I would like to release Apache Commons
Text 1.15.0.
Apache Commons Text 1.15.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/text/1.15.0-RC1
(svn revision 81187)
The Git tag commons-text-1.15.0-RC1 commit for this RC is
04e937470d3679cc163df85d82d5b6d2e3e71128 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=04e937470d3679cc163df85d82d5b6d2e3e71128
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-text.git
--branch commons-text-1.15.0-RC1 commons-text-1.15.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1886/org/apache/commons/commons-text/1.15.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Thu Dec 04 15:57:23 UTC 2025
commons-text-1.15.0-bin.tar.gz=6d1fcbd85a85f38e95ea33c9ab7f58798723b0e6357077246a135c417e75c7b39e278ebdb77fcc8f9b56b52b1eeff113eea9463eaaaee8d38df9afdc149b6421
commons-text-1.15.0-bin.zip=b3c2e911dffb363ebad514f6ec5033c4aeb1151489fb7d644a5594d9a967d82900293695f34c1bf68f63eca931048cb427e6d6a97853a60bc084028984ad4394
commons-text-1.15.0-bom.json=be56a3b231df3c10515625b51ee4307b969a25cf158933ec4d285b28d5e9b9cbb65278e0b186bcc0728ada2a9445021fa24672e3a12a09c56a45e8658e2fafbf
commons-text-1.15.0-bom.xml=1489264975fd7333852bcad5cd9df2b0405a643de346990e8a5bffe565d50a13fa623c14ae86fb4c1f00c8e8318eda414c180dafc4912a98519445e887f28600
commons-text-1.15.0-javadoc.jar=b108a1d3fe44a82fee6d18bd6810018fa26da55b2896142bb7fa2517b5088d3306f64f11d33d5e5608b02718e7ec1d52c256ad7bf4a49bed607c12825be6ec18
commons-text-1.15.0-sources.jar=580f1fc506f3dbc826e79f53ca7758e933e310cb4021bc8f2dd3b2322bd3e67bd6a87becbb9a499cee5fa16393fd0fac28b68f67c0fe914279b3fec93a917bcb
commons-text-1.15.0-src.tar.gz=5bbeebbe5853525d72a54ad483344f2a55b360cb3abeeada2eb52ca6118f10102bb8fb8ca42417c38b6f8ed7147807414f50c5093473fac9fd3f74cfb8160958
commons-text-1.15.0-src.zip=7469be2546687cb47c8276e57ae8163a1fc8612cd74c93b3a8b1e495366ab60f24181d5a48470439e48fa8c15f52f50b80452b76c5c59ec8b129e7e311501583
commons-text-1.15.0-test-sources.jar=030f9dcd909378e492f93db7e9fcf6783d8589f264f3e6e36a46f70218633fee4231d9bd3a62478d1aac62dcce82f7c7a8136d996bd4cbf03bb56a8de6244044
commons-text-1.15.0-tests.jar=7fe74947c1011c0f77405f8b02e54a6047b7ab67eedb91dc9cac11ac4b61745b15b4b5bf5ff206f60bad4b92599d624fe15de8c75d0d7795c48c6e1acea1cbf0
org.apache.commons_commons-text-1.15.0.spdx.json=bc1b2ddf0e65c34592d5a93b4b95f5f52b8b4ff62cb3dfe8aaa7ae0dcb77ec835712a2b2f203efde4d68c1ef9755bf4c32e7ac607d2156e192d2bffe43a72675
I have tested this with 'mvn' and 'mvn clean install site' using:
openjdk version "25.0.1" 2025-10-21
OpenJDK Runtime Environment Homebrew (build 25.0.1)
OpenJDK 64-Bit Server VM Homebrew (build 25.0.1, mixed mode, sharing)
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec
Java version: 25.0.1, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk/25.0.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.7.2", arch: "aarch64", family: "mac"
Darwin ****-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Wed
Oct 15 21:12:15 PDT 2025;
root:xnu-11417.140.69.703.14~1/RELEASE_ARM64_T6041 arm64
Docker version 28.4.0, build d8eb465
Details of changes since 1.14.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/text/1.15.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/text/1.15.0-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/text/1.15.0-RC1/site/index.html
(note some *relative* links are broken and the 1.15.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 1.14.0):
https://dist.apache.org/repos/dist/dev/commons/text/1.15.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/text/1.15.0-RC1/site/rat-report.html
KEYS:
https://downloads.apache.org/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now.
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
Thank you,
Gary Gregory,
Release Manager (using key 530AA5F25C25011F)
The following is intended as a helper and refresher for reviewers.
Validating a release candidate
==============================
These guidelines are NOT complete.
Requirements: Git, Java, and Maven.
You can validate a release from a release candidate (RC) tag as follows.
1a) Download and decompress the source archive from:
https://dist.apache.org/repos/dist/dev/commons/text/1.15.0-RC1/source
1b) Check out the RC tag from git (optional)
This is optional, as a reviewer must check source distributions as a minimum.
git clone https://gitbox.apache.org/repos/asf/commons-text.git
--branch commons-text-1.15.0-RC1 commons-text-1.15.0-RC1
cd commons-text-1.15.0-RC1
2) Checking the build
All components should include a default Maven goal, such that you can
run 'mvn' from the command line by itself.
2) Check Apache licenses
This step is not required if the site includes a RAT report page which
you then must check.
This check should be included in the default Maven build, but you can
check it with:
mvn apache-rat:check
3) Check binary compatibility
This step is not required if the site includes a JApiCmp report page
which you then must check.
This check should be included in the default Maven build, but you can
check it with:
mvn verify -DskipTests -P japicmp japicmp:cmp
4) Build the package
This check should be included in the default Maven build, but you can
check it with:
mvn -V clean package
You can record the Maven and Java version produced by -V in your VOTE reply.
To gather OS information from a command line:
Windows: ver
Linux: uname -a
4b) Check reproducibility
To check that a build is reproducible, run:
mvn clean verify artifact:compare -DskipTests
-Dreference.repo=https://repository.apache.org/content/repositories/staging/
'-Dbuildinfo.ignore=*/*.spdx.json'
Note that this excludes SPDX files from the check.
5) Build the site for a single module project
Note: Some plugins require the components to be installed instead of packaged.
mvn site
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html
-the end-
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
