Using generated Kotlin from JPMS #77

New Issue

2025-12-30T01:20:27+01:00

adam commented

2025-12-30 01:20:27 +01:00

Originally created by @sgammon on GitHub (Feb 18, 2024).

I've run into an issue with generated Pkl code in Kotlin. There does not appear to be an option in the Gradle plugin to set a package path; as a result, generated Kotlin ends up in the root package, which can't be exported from a Java module.

This could be fixed by adding an input argument to the code generator which sets a package path, to be included as package ... at the top of the generated code files.

Originally created by @sgammon on GitHub (Feb 18, 2024). I've run into an issue with generated Pkl code in Kotlin. There does not appear to be an option in the Gradle plugin to set a package path; as a result, generated Kotlin ends up in the root package, which can't be exported from a Java module. This could be fixed by adding an input argument to the code generator which sets a package path, to be included as `package ...` at the top of the generated code files.

adam referenced this issue

2025-12-30 01:24:17 +01:00

[PR #77] [MERGED] fix wrong stdlib doc links (#74) #397

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/pkl#77