We have fixed a few bugs and one enhancement (Java 16 records) since
Apache Commons BCEL 6.8.2 was released, so I would like to release
Apache Commons BCEL 6.9.0.

Apache Commons BCEL 6.9.0 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1 (svn
revision 68692)

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

Maven artifacts are here:
    
https://repository.apache.org/content/repositories/orgapachecommons-1724/org/apache/bcel/bcel/6.9.0/

These are the artifacts and their hashes:

#Release SHA-512s
#Sun Apr 21 17:07:12 UTC 2024
bcel-6.9.0-bin.tar.gz=e2ac07716a8203405040a18e6dddb84445c0cbc874da382fc67b082c20f3659228ecabf6cba3fbe83b60d36d08c2d9493dfd731960f5aec073f87d9f2e8126f2
bcel-6.9.0-bin.zip=93efcf6194077fc216ca81a0f37ca6dc2f5e4032483cfee34c789fe859917be0924221c502ed886fb4582e3681907e73e4f5af11591d1d6a6b2fd779b871bbda
bcel-6.9.0-bom.json=4c085990c8b5ece5092f8032b56fd7c87a686443f37b04a2701904b37d7fb1f7147013f82110d67b12d449b78d4743634112f5fa9bfa80de03ec71a06755d934
bcel-6.9.0-bom.xml=5759c53a32588f25d672daf90955cee7e2f21a60d98b06a2a8d0fb15ff5308f90885a87eadfbd835cb5b86c856866daac5af04f6723d28495118e984d1d3eff4
bcel-6.9.0-javadoc.jar=ac65e56220c0b8fffd67d03a2b003631c34742f33e385249a3b9c511fce50574771afc800ae6d8521ef6195cfc0f448f64b7b7b21a4d80cfe6ba7af86dd1fb19
bcel-6.9.0-sources.jar=5e9f448c48604edbfcc2416994649d118e58de596212cd034dc21895277829f8540e43f76f3e45396fa29a060b17b1e1b9086068043131e7f771213449a18349
bcel-6.9.0-src.tar.gz=d0a7099257ee30e1ff56896d3d855ba03d2d3efb92a9ac0fba7464ef3052ab26ad7c8ed3a37e551ad5f944a0f04cc811047b20f90c81133ab9aaa008bf517da4
bcel-6.9.0-src.zip=37b632c1f921a8aa476571085ce43bdf63db8150a94640775c7bc56d737613cd24e5531a236223ab3ee2e0b15416f3a5722012edd126defdd0f5f8e6ea6c11d0
bcel-6.9.0-test-sources.jar=9f9d9a56fb477f767ac9d3e7637a4ef1de032d70594bba3c0999b8a616de73d3ba590f32a154d2699efb0ae2a0932e97229e2dba25758402b6412112086afb95
bcel-6.9.0-tests.jar=f645062309b71990440ada1b7cea4b37a24eadcefbe7e0c7a2358905516d713172704c8cfe6f765d89bf8e4a60bfa51096b42efebbe0b5a249f7dc3fecad3e4c
org.apache.bcel_bcel-6.9.0.spdx.json=52ee76059ef22938aabbe6fb62d3d71bc3289d38c2b2cac4ddb415b8e7603c90af9cad33baa9d583f6baf96c1206b66c85fb5576e372473cf3ec1939f3792ea9



I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
jacoco -P japicmp clean package site deploy' using:

openjdk version "17.0.11" 2024-04-16
OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)

Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 17.0.11, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"

Darwin **** 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64

Details of changes since 6.8.2 are in the release notes:
    
https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1/RELEASE-NOTES.txt
    
https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1/site/changes-report.html

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

JApiCmp Report (compared to 6.8.2):
    
https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1/site/japicmp.html

RAT Report:
    
https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.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 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-bcel.git
--branch commons-bcel-6.9.0-RC1 commons-bcel-6.9.0-RC1
cd commons-bcel-6.9.0-RC1

1b) Download and unpack the source archive from:

https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-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: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to