Skip to content

Fix IllegalAccessError in the forked JVM on Java 8 and 11 (#3511) - #3513

Merged
olamy merged 1 commit into
apache:masterfrom
olamy:GH-3511
Oct 8, 2026
Merged

olamy merged 1 commit into
apache:masterfrom
olamy:GH-3511

Conversation

@olamy

@olamy olamy commented Oct 8, 2026

Copy link
Copy Markdown
Member

Only look up the enclosing classes of scanned classes when a class fails
the include/exclude patterns, rather than doing it for every class up front.
If Java 8 or 11 still throws during that lookup, work the names out from
the class name instead of crashing the fork.

Signed-off-by: Olivier Lamy olamy@apache.org


To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
check one of the following:

Only look up the enclosing classes of scanned classes when a class fails
the include/exclude patterns, rather than doing it for every class up front.
If Java 8 or 11 still throws during that lookup, work the names out from
the class name instead of crashing the fork.

Signed-off-by: Olivier Lamy <olamy@apache.org>
@olamy olamy added this to the 3.6.1 milestone Oct 8, 2026
@olamy olamy self-assigned this Oct 8, 2026
@olamy olamy added the bug Something isn't working label Oct 8, 2026
@olamy
olamy merged commit 7763309 into apache:master Oct 8, 2026
16 checks passed
@olamy
olamy deleted the GH-3511 branch October 8, 2026 23:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3.6.0 leads to java.lang.IllegalAccessError (with forking/toolchain?) and very slow run (otherwise)

1 participant