DO NOT REPLY [Bug 9246] New: - constant pool does not have unused entries removed after calling getFinalConstantPool

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9246>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9246

constant pool does not have unused entries removed after calling getFinalConstantPool

           Summary: constant pool does not have unused entries removed after
                    calling getFinalConstantPool
           Product: BCEL
           Version: 5.0RC1
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Main
        AssignedTo: [email protected]
        ReportedBy: [email protected]


I have been trying to use the BCEL api to work out which methods and fields in
a collection of java class files are unused and can be removed. This was 
relatively easy.

Unfortunately when using the BCEL api to actually remove methods and fields it 
would appear that the constant pool is left unaltered by this removal 
procedure. I.e. the names of fields and methods which now no longer exist are 
still apparent in the constant pool.

I had assumed that assigning the result of calling getFinalConstantPool to be 
the java classes new constant pool would do this.

It does not