commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benedikt Ritter <>
Subject [VOTE] Release Apache Commons BCEL 6.0 based on RC7
Date Sat, 02 Jul 2016 18:52:09 GMT

I'd like to release Apache Commons BCEL 6.0 based on RC7. Changes compared
to RC6 are:

- restored binary compatibility to a greater degree
- fixed issue BCEL-262

BCEL 6.0 RC7 is available for review here: (svn revision 14251)

The tag is here: (svn
revision 1751084)

Maven artifacts are here:

These are the Maven artifacts and their hashes

  (SHA1: f1e1534867a901b9ba4884e5805317635c324589)
  (SHA1: 9ba3b50aa95289d01ec119b60be68eb4c608ba1d)
  (SHA1: 484b29d3a73fbe0c103d85965c4fd22e6253f545)
  (SHA1: f8b5857f3245e10548ef29cf7006c045b913a199)
  (SHA1: fe1ecaf2ba3b1f9f18cdde4f13943e3ccc1d5e69)
  (SHA1: ea17ee1b2c28804437212970ea2d273efeb3807e)

I have tested this with JDK 7, 8 using Maven 3.3.9.

Details of changes since 1.1 are in the release notes:

(note some *relative* links are broken and the 6.0 directories are not yet
created - these will be OK once the site is deployed)

Clirr Report (compared to 5.2):

Note that Clirr reports 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 org.apache.bcel.classfile.Visitor interface: OK because
that does not affect binary compatibility.
- Removed from all classes: OK, because we don't
expect anybody to rely on serialization for BCEL classes
- Return type of method 'public java.lang.Object getElementAt(int)' has
been changed to java.lang.String in class
org.apache.bcel.verifier.VerifierFactoryListModel: OK, because this class
is part of an UI application and for this reason should only used by Swing.

RAT Report:


Please review the release candidate and vote. This vote will close no
sooner that 72 hours from now, i.e. sometime after 21:00 CEST 05-July 2016

[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message