We have made some enhancements since Apache Commons Parent 64 was
released, so I would like to release Apache Commons Parent 65.
Apache Commons Parent 65 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/65-RC1 (svn
revision 65392)
The Git tag commons-parent-65-RC1 commit for this RC is
d6b68690bead91ce5ac31347df2d56f48aa97489 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=d6b68690bead91ce5ac31347df2d56f48aa97489
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-65-RC1 commons-parent-65-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1673/org/apache/commons/commons-parent/65/
These are the artifacts and their hashes:
#Release SHA-512s
#Fri Nov 17 21:03:32 EST 2023
commons-parent-65-bom.json=b2f18d4e4da464cb3b677d6f474da13b3c728cbbdeed82dda6a0d21c903352da4220635557e6d08d4240b0cb4f67268759bcddc037cc80f9976dea69f072f09e
commons-parent-65-bom.xml=5b59a00e18ed0a71dbbc8b47eaf9f84f35ac066ea94ee47ff1fc0580c8dd602b74cd122b909e97e5359e74bc6b164025da9858d53ed14e382a97edde7ac17a14
commons-parent-65-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-65-src.tar.gz=afc826950640e31bf61a16d61a953ddbf479a5ed8018a1051246802364c1eeef9aeb523233086837963db236ccc812b0007a381ef1394362a54c92031c9ce82e
commons-parent-65-src.zip=8ae1a2a7e97d39f231aac0e20cc16724d5aecee62256c472496058d1fcd11e07f3c92d1515d5a42f41a0ce5d8282db734b6c21a9dd996861b5b7336f68fcdce6
org.apache.commons_commons-parent-65.spdx.json=a9814adf2044737f18936037ef5427e7b3d2ce01d5e1f5516d4efcd411f7b532f97f5225da640667dc4fcf286bda1052f274875653698630fcde6458d74faa68
I have tested this with
mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
Using:
Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: /usr/local/Cellar/maven/3.9.5/libexec
Java version: 21.0.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.1.1", arch: "x86_64", family: "mac"
Darwin gdg-mac-mini.local 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct
9 21:27:27 PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 x86_64
Details of changes since 64 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/65-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/65-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/65-RC1/site/index.html
(note some *relative* links are broken and the 65 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/65-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 86fdc7e2a11262cb)
For following is intended as a helper and refresher for reviewers.
Validating a release candidate
==============================
These guidelines are NOT complete.
Requirements: Git, Java, Maven.
You can validate a release from a release candidate (RC) tag as follows.
1a) Clone and checkout the RC tag
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-65-RC1 commons-parent-65-RC1
cd commons-parent-65-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/65-RC1/source
2) Check Apache licenses
This step is not required if the site includes a RAT report page which
you then must check.
mvn apache-rat:check
3) Check binary compatibility
Older components still use Apache Clirr:
This step is not required if the site includes a Clirr report page
which you then must check.
mvn clirr:check
Newer components use JApiCmp with the japicmp Maven Profile:
This step is not required if the site includes a JApiCmp report page
which you then must check.
mvn install -DskipTests -P japicmp japicmp:cmp
4) Build the package
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]
