We have fixed one issue and updated some dependencies since the
release of Apache Commons Parent 103, so I would like to release
Apache Commons Parent 104.

All Java 8 builds are currently broken with the same Javadoc error:

Error fetching URL: https://jakarta.ee/specifications/platform/8/apidocs/

Java EE 8 Javadoc has been republished with a Java version > 8 and is
no longer compatible with Javadoc 8.

Because of this, I am reducing the VOTE window from 72 to 24 hours.

Apache Commons Parent 104 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/parent/104-RC1 (svn
revision 86891)

The Git tag commons-parent-104-RC1 commit for this RC is
9066f72892fba9af187520ba37889ae068a333ba, which you can browse here:
    
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=9066f72892fba9af187520ba37889ae068a333ba
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-104-RC1 commons-parent-104-RC1

Maven artifacts are here:
    
https://repository.apache.org/content/repositories/orgapachecommons-1958/org/apache/commons/commons-parent/104/

These are the artifacts and their hashes:

#Release SHA-512s
#Thu Aug 20 14:25:02 UTC 2026
commons-parent-104-bom.json=00455ad8005b512f5d16c00b0117d505e9e8daa6c70f7fab3c2a493a05e2702b00d7297a70ece693c55cb0453d1b6cf58609187cb498a83ecdedfed15cf04666
commons-parent-104-bom.xml=fdb4594bfc35a887c7120f63b9303db359fe013a066fd95a588df46769d03853a61da914ee19ab1479ac1c41c939ed1b8ee15eb5de5346aa28aff113ec45e528
commons-parent-104-site.xml=78fbbc6f0f79a0b7c86f7b298675fba49f01f44f08b2211e41a727835c38c4e32e33fb20cf39284ad33afb427116e6a667888f50f87b5f98d64c23788bb7fd3a
commons-parent-104-src.tar.gz=00828764d4ad976691e5d3dad7139a609dd331021bd0d5053c80c4e1f542ee3beab540d3b4980840dcfa6f59ff93c24db338628a2ef06f6eefb81a91cb7f951d
commons-parent-104-src.zip=230a8499233fbdae2ae34018409e017c07f42d3df47cc37f9532458ee4bd674290c629145559e2d9c4b5c20b14cff3c693167ea8d2e8d98753a951c22dd2ce1b
org.apache.commons_commons-parent-104.spdx.json=8f68dc206d484f3fb69a0d1b742c645918a689383c9e40515aed872ff91db0809cabc322505657a162494a573babad841029940b8c67493946c6f0ce6d07824b


I have tested this with 'mvn' and 'mvn clean install site' using:

openjdk version "21.0.12.1" 2026-08-18
OpenJDK Runtime Environment Homebrew (build 21.0.12.1)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.12.1, mixed mode, sharing)

Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5)
Maven home: /opt/homebrew/Cellar/maven/3.9.16/libexec
Java version: 21.0.12.1, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.12.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "26.6.2", arch: "aarch64", family: "mac"

Darwin Garys-MacBook-Pro.local 25.6.0 Darwin Kernel Version 25.6.0:
Fri Jul 31 19:17:26 PDT 2026;
root:xnu-12377.161.14~5/RELEASE_ARM64_T6041 arm64

Docker version 29.7.2, build a7dcaa6


Details of changes since 103 are in the release notes:
    
https://dist.apache.org/repos/dist/dev/commons/parent/104-RC1/RELEASE-NOTES.txt
    
https://dist.apache.org/repos/dist/dev/commons/parent/104-RC1/site/changes.html

Site:
    
https://dist.apache.org/repos/dist/dev/commons/parent/104-RC1/site/index.html
    (Note some *relative* links are broken and the 104 directories are
not yet created - these will be OK once the site is deployed.)

RAT Report:
    
https://dist.apache.org/repos/dist/dev/commons/parent/104-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 24 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/parent/104-RC1/source

1b) Check out the RC tag from git (optional)

This is optional,  as a reviewer must at least check source distributions.

git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-104-RC1 commons-parent-104-RC1
cd commons-parent-104-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]

Reply via email to