We have fixed one important bug since Apache Commons BCEL 6.4.0 was
released, so I would like to release Apache Commons BCEL 6.4.1.
Apache Commons BCEL 6.4.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/bcel/6.4.1-RC1 (svn
revision 36085)
The Git tag commons-bcel-6.4.1-RC1 commit for this RC is
bebe70de81f2f8912857ddb33e82d3ccc146a24e which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=bebe70de81f2f8912857ddb33e82d3ccc146a24e
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-bcel.git --branch
commons-bcel-6.4.1-RC1 commons-bcel-6.4.1-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1472/org/apache/bcel/bcel/6.4.1/
These are the artifacts and their hashes:
#Release SHA-512s
#Thu Sep 26 21:15:47 EDT 2019
bcel-6.4.1-bin.tar.gz=937994f22aaaf7dfe1f9a789f6c9968f80b5c9a2929aa0364beffe1b9136f7af98dd6386533f02441f74a9df57e913b4eb9c0598778f31d4ea3cda9b02beabcb
bcel-6.4.1-bin.zip=94bcd0afa9f6679f7d0e25b5bf3d2901d7e42f4488f6b7f2a5b91827023ca56ef6c5bf2b82996ec196d2b744f1345526f729dc00b3fb58d4b55f8fa7748e5fa1
bcel-6.4.1-javadoc.jar=280a79bc811c4c8b9c0249ba98d82a0054dd286ee1009f340231ac9d147709e06800e50c26fd21d8f31d15ab337a9ae30727edd8548f269d968ca7f31eb72abf
bcel-6.4.1-sources.jar=5761d9e1ba53b9d60f81941f1db581030aaadb5829f429c2897220c13874a7718e26f213bd9f49bbed68fb0a3a8e6375f312ce4c8cd551030d95652209aa7ab2
bcel-6.4.1-src.tar.gz=746987c314d3a2bd7308e5cd0b3403c915f09b5127af5980f986a81bccff91cca6098b636fd2f337e8e42f1e3600e8eac14b4f3b0564739b155955603a2e9b7f
bcel-6.4.1-src.zip=b63f3d53ec3c9cc623475c2383e292aa5fd52f1a8388c162a86b345efd82b3ba199b3ff096baf9a7a4767317b0c928d828c01154394e39bcecf9577668d7b1a6
bcel-6.4.1-test-sources.jar=28dd0b17d43552b9b91aed3c1fac042b388f50deaf3953930ce69906e8269ae5850dd402b93f7641266c665c6fd72069f025a590a6f39e907b084ea4db100517
bcel-6.4.1-tests.jar=5168dab87d4b49861f4dc8e0fc3522e26175a5faa3010cb5127b0455190c16246f35cf0b86b48ecdc92e4b4107197cef3c1265aade6ba630eb32dcd87ceb9fd7
I have tested this with:
mvn -V -Duser.name=%my_apache_id%
-Dcommons.release-plugin.version=1.7-SNAPSHOT -Ddoclint=none -Prelease
-Ptest-deploy clean package site deploy
using:
Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117;
2019-08-27T11:06:16-04:00)
Maven home: C:\Java\apache-maven-3.6.2\bin\..
Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk1.8.0_221\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Details of changes since 6.4.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/bcel/6.4.1-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/bcel/6.4.1-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/bcel/6.4.1-RC1/site/index.html
(note some *relative* links are broken and the 6.4.1 directories are
not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 6.4.0):
https://dist.apache.org/repos/dist/dev/commons/bcel/6.4.1-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/bcel/6.4.1-RC1/site/rat-report.html
KEYS:
https://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner that 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.
1) Clone and checkout the RC tag
git clone https://gitbox.apache.org/repos/asf/commons-bcel.git --branch
commons-bcel-6.4.1-RC1 commons-bcel-6.4.1-RC1
cd commons-bcel-6.4.1-RC1
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
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
6) Build the site for a multi-module project
mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html
-the end-
