+1 all looks good across the builds, reports, A little surprised that we have a bunch of fiiles under src/example without the apache license in the header. And that the java files under src/test/resources also don’t have the apache license (which I could see there being a case for this if we’re doing heavy file level manipulation, but still feels like they should be there).
> On Jan 18, 2026, at 9:43 PM, Gary Gregory <[email protected]> wrote: > > We have fixed a few bugs and added enhancements since the release of > Apache Commons BCEL 6.11.0, so I would like to release Apache Commons > BCEL 6.12.0. > > Apache Commons BCEL 6.12.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/bcel/6.12.0-RC1 > (svn revision 81960) > > The Git tag commons-bcel-6.12.0-RC1 commit for this RC is > fc617c0ff5046732b769bfbee39b73858d1db346, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=fc617c0ff5046732b769bfbee39b73858d1db346 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-bcel.git > --branch commons-bcel-6.12.0-RC1 commons-bcel-6.12.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1910/org/apache/bcel/bcel/6.12.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Jan 18 22:28:49 UTC 2026 > bcel-6.12.0-bin.tar.gz=b723568e2641d09971275a8d0914cc5515d0c60333e9fb7d70f777449e0ab600c70defcc1fd71fa076c52c7acd3d925fed0349d6607dfc6fe06ada0bf1919bbc > bcel-6.12.0-bin.zip=5e7d3ba3423d0b7f37ae680025aebe3616c439ca983673d1053b134a3c27e4c398a8a78d0878695ad8f945e738d71fbe97a6e6775cc5ca8ec7c6ba1adb796ade > bcel-6.12.0-bom.json=e9dfcb7270a6466f3058785ff11b405f8805f025783f6c4778eef43726b1fe23a11d84bd9d49fa1ad0fc803d55033771109183449850fb81b39c35507dce2e1c > bcel-6.12.0-bom.xml=49478817efc98f508ee7032d438eeaf2e237be2b9c83dc8c5edae32bcc98057d97008e6ec75f419352f90428ef0d6ebcfa224ab763111a2c09d8420baa049742 > bcel-6.12.0-javadoc.jar=9b29473dfa4a8bba2ea7e14e8e44a35194d20f8fb0e1d2ac24b5620287c310f8d83f0aca8dde36622f67a8ce87c3bdd4beedd500ebc322b4b29546d5322bbfa9 > bcel-6.12.0-sources.jar=6ec87cffda0e65d3ebd653d6f0fa9173556ae90514ea6c0e4d4cf5c1ca7badd084430da3c94ed36ba1cf12fb2603f99d46cbcfcf1c62e36e6c7394b552f42b48 > bcel-6.12.0-src.tar.gz=0633e4ba82e8648a556a3e2e8dc3e43c3f2b8ff8c6000ff06cebfb816e86f73d463b047fa0ca39c04bc7c89fe0a5e42d892b17608c204799cb7ecc9aa5a01a71 > bcel-6.12.0-src.zip=4d4b41227dd84451bb622fb8c2a43c35213d142b9f86e2030cefeaf67f3cb2fb74d2200ca638ef682a5473f6c352f2089021bbbb04dd750db984a2ce983f5f8d > bcel-6.12.0-test-sources.jar=f5a4275f125c3347ef30aba8a57d01a52b4e2cef84f3827dd0c3d3a68d8c3f4066d97e66f7ab043e05bc1077af3e91e5e3d1208a17e898325a0a24254a9acb4d > bcel-6.12.0-tests.jar=eefdc275664fcc605075d0f2a7de66b59a519834106845f88683fa5770478626e75a64247cc989120b6168dd0adf3db5a5e8efbdead274b2c47ae8e3892be145 > org.apache.bcel_bcel-6.12.0.spdx.json=4d11d8b08a6a3306e953c46d3e24f25c946de811187212e7fd4da4011fe2d6891a67a3dfc6235d27782647fecd3597bd7e80fa0fd769ba2d4847d8fab365fa07 > > > > I have tested this with 'mvn' and 'mvn clean install site' using: > *** > Use the output from "mvn -version" for each combination you tested. > Windows: ver > Linux: uname -a > *** > > Details of changes since 6.11.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.12.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.12.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.12.0-RC1/site/index.html > (Note some *relative* links are broken and the 6.12.0 directories > are not yet created - these will be OK once the site is deployed.) > > *** JApiCmp Report (compared to 6.11.0): > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.12.0-RC1/site/japicmp.html > > *** > Note that the above report notes several errors. > These are considered OK for the reasons stated below. > These exceptions are also noted in the Changes and Release Notes. > > Errors reported: > - methods added to interface: OK because that does not affect > binary compatibility. > - etc. > *** > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/bcel/6.12.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 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/bcel/6.12.0-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-bcel.git > --branch commons-bcel-6.12.0-RC1 commons-bcel-6.12.0-RC1 > cd commons-bcel-6.12.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 > > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
