We have fixed a few bugs and added enhancements since Apache Commons
Skin 5.0.0 was released, so I would like to release Apache Commons
Skin 5.1.0.
The primary goal of this release is to utilize the new Apache Commons Oak logo.
Apache Commons Skin 5.1.0 RC1 is available for review, but there is no
website generated for this review. If you generate the site locally,
you'll notice that it still carries the old logo because it uses the
current commons-parent POM. Once commons-skin is released,
commons-parent can be updated to use the new commons-skin version
which will then cause new sites to carry the new logo.
The Git tag commons-skin-5.1.0-RC1 commit for this RC is
477a8e4eb2059b4bd260d25b1a91bed82756e6fb which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-skin.git;a=commit;h=477a8e4eb2059b4bd260d25b1a91bed82756e6fb
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-skin.git
--branch commons-skin-5.1.0-RC1 commons-skin-5.1.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1860/org/apache/commons/commons-skin/5.1.0/
I have tested this with 'mvn' and 'mvn clean install site' using:
openjdk version "21.0.8" 2025-07-15
OpenJDK Runtime Environment Homebrew (build 21.0.8)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.8, mixed mode, sharing)
Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b)
Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec
Java version: 21.0.8, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.8/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.6.1", arch: "aarch64", family: "mac"
Darwin ****.local 24.6.0 Darwin Kernel Version 24.6.0: Mon Jul 14
11:30:40 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T6041 arm64
Docker version 28.3.2, build 578ccf6
Details of changes since 5.0.0 are in the release notes:
https://github.com/apache/commons-skin/tree/commons-skin-5.1.0-RC1/RELEASE-NOTES.txt
https://github.com/apache/commons-skin/tree/commons-skin-5.1.0-RC1/src/changes/changes.xml
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 86fdc7e2a11262cb)
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.
1) Check out the RC tag from git
git clone https://gitbox.apache.org/repos/asf/commons-skin.git
--branch commons-skin-5.1.0-RC1 commons-skin-5.1.0-RC1
cd commons-skin-5.1.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
Does not apply for commons-skin.
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
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]
