Skip to content

Let callers supply the class hierarchy when patching a JAR - #2

Merged
lbialy merged 3 commits into
VirtusLab:masterfrom
Gedochao:fix/jar-processor
Aug 10, 2026
Merged

Let callers supply the class hierarchy when patching a JAR #2
lbialy merged 3 commits into
VirtusLab:masterfrom
Gedochao:fix/jar-processor

Conversation

@Gedochao

@Gedochao Gedochao commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Fixes #1

Gedochao and others added 2 commits August 10, 2026 13:27
� Conflicts:
�	build.sbt
�	cli/src/main/scala/sloth/cli/Main.scala
�	core/src/main/scala/sloth/patching/BytecodePatcher.scala
�	core/src/main/scala/sloth/patching/ClassLoaderClassWriter.scala
…ynamic Class.forName, which fails under GraalVM without reflection metadata.

Co-authored-by: Cursor <cursoragent@cursor.com>

@lbialy lbialy left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed extensively with the author, the concept is correct for the use case (native-image compilation). There are some gotchas but reporting of unresolvable classes is the correct choice for now.

@lbialy
lbialy merged commit ed68a4a into VirtusLab:master Aug 10, 2026
5 checks passed
@Gedochao
Gedochao deleted the fix/jar-processor branch August 10, 2026 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ClassLoaderClassWriter silently falls back to Object; JarProcessor should accept a caller-provided resolver

2 participants