Skip to content

Getting the annotation processor working when I'm using kotlin, gradle and kapt.#75

Merged
andreaTP merged 1 commit into
bytecodealliance:mainfrom
RefuX:fix/wasm-classpath-resolution
Jun 29, 2026
Merged

Getting the annotation processor working when I'm using kotlin, gradle and kapt.#75
andreaTP merged 1 commit into
bytecodealliance:mainfrom
RefuX:fix/wasm-classpath-resolution

Conversation

@RefuX

@RefuX RefuX commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Hi there,

I has having trouble getting @WasmModuleInterface working with my Kotlin class.

After a bit of digging turns out it was mainly a maven/gradle difference with the assumptions about where resources are placed.

The fix is simply to make WasmModuleProcessor a bit more generous about where it will look for the wasm file.

@RefuX RefuX requested a review from andreaTP as a code owner June 29, 2026 11:21
@andreaTP

Copy link
Copy Markdown
Contributor

I agree the current implementation is too restrictive.

Do you mind removing the wildcard import to get CI green?

@RefuX RefuX force-pushed the fix/wasm-classpath-resolution branch from b23c689 to 074f527 Compare June 29, 2026 13:18

@andreaTP andreaTP left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM, thanks for taking the time to improve it!

@andreaTP andreaTP merged commit 5d85eb1 into bytecodealliance:main Jun 29, 2026
25 checks passed
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.

2 participants