You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Thomas Rebele (Jira)" <ji...@apache.org> on 2026/07/10 13:33:00 UTC
[jira] [Commented] (CALCITE-7649) Add bytecode verification check using ASM in the gradle build
[ https://issues.apache.org/jira/browse/CALCITE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095298#comment-18095298 ]
Thomas Rebele commented on CALCITE-7649:
----------------------------------------
I prepared a PR based on a proposal from [~zabetak]. I've included [~rubenql]'s fix for CALCITE-6393 to avoid build errors.
> Add bytecode verification check using ASM in the gradle build
> -------------------------------------------------------------
>
> Key: CALCITE-7649
> URL: https://issues.apache.org/jira/browse/CALCITE-7649
> Project: Calcite
> Issue Type: Improvement
> Reporter: Thomas Rebele
> Assignee: Thomas Rebele
> Priority: Major
> Labels: pull-request-available
>
> CALCITE-6393 has shown that JDK bugs might produce invalid bytecode. This can lead to problems in downstream projects (e.g., [Apache Pinot|https://github.com/apache/pinot/issues/15119], or in a [PR for HIVE-29641|https://github.com/apache/hive/pull/6523]).
> This ticket aims to add a verification step that detects invalid bytecode during build.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)