You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2022/08/15 18:04:00 UTC

[jira] [Resolved] (BCEL-362) Handling for Constants.CONSTANT_Dynamic is missing in class ConstantPool

     [ https://issues.apache.org/jira/browse/BCEL-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary D. Gregory resolved BCEL-362.
----------------------------------
    Fix Version/s: 6.6.0
       Resolution: Fixed

In git master and the snapshot repo at  https://repository.apache.org/content/repositories/snapshots/org/apache/bcel/bcel/6.6.0-SNAPSHOT/

Please verify and close.

> Handling for Constants.CONSTANT_Dynamic is missing in class ConstantPool
> ------------------------------------------------------------------------
>
>                 Key: BCEL-362
>                 URL: https://issues.apache.org/jira/browse/BCEL-362
>             Project: Commons BCEL
>          Issue Type: Bug
>            Reporter: Alexander Kriegisch
>            Priority: Major
>             Fix For: 6.6.0
>
>
> _Disclaimer: I am not a byte code buff, so if I am misunderstanding anything here, please forgive me for raising a stupid issue, try to be patient and explain it to me._
> When looking at the class {{[ConstantPool|https://github.com/apache/commons-bcel/blob/5165671d2bc4bed17918051f1689ee5fd4c3425a/src/main/java/org/apache/bcel/classfile/ConstantPool.java]}}, it seems as if condy is not being handled in methods
> * {{constantToString(Constant)}},
> * {{addConstant(Constant, ConstantPool)}},
> * {{addConstantDynamic(int, int)}} (method does not exist, not sure if it would be necessary).
> I would have expected something like {{case Constants.CONSTANT_Dynamic}} with proper handling for this case in the first two methods. 
> When using BCEL in order to parse class files using condy, like JaCoCo creates them, this causes errors. FYI, we are using BCEL code in AspectJ, and whenever people combine it with JaCoCo, corresponding problems occur.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)