On Thu, 25 Sep 2025 20:11:15 GMT, Chen Liang <[email protected]> wrote:
>>> Last time I tried to migrate off BCEL to ClassFile API, I noted only xalan >>> xsltc is using it to write class files. Is it possible for us to remove it >>> in the long run? >> >> Remove just BCEL or even XSLTC? > > @jdlib If we need to maintain a patched (to remove extra dependencies) BCEL, > I believe we are better off maintaining a patched (to use ClassFile API > instead of BCEL) xsltc. @liach Refactoring XSLTC to use the classfile API seems to be a quite straightforward exercise (e.g. moving all use of BCEL classes into xsltc.MethodGenerator, (new) xsltc.InstructionList etc and then redirect their implementation to the classfile API), but not sure if the result can then be easily patched. On the other hand there may not be that much activity on the Apache XSLTC side anymore. I would almost like to volunteer for such a migration. ------------- PR Comment: https://git.openjdk.org/jdk/pull/27459#issuecomment-3341444475
