You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the package name for the classes generated from Pkl modules (when using the Gradle plugin or the CLI) is always derived from the module name defined within the Pkl module file:
open module org.example.Whatever
This is, however, not very flexible, because there are use cases when the module name's prefix and the desired Java/Kotlin package name may differ. For example, when publishing Pkl packages (with PklProject) it is expected that the module name prefix matches the Pkl package name:
// Within package://some-repo.com/some-org/[email protected]#/SomeModule.pkl:
open module some_package.SomeModule
...
However, if a project already uses some particular JVM package name, it would be necessary either to change the Pkl package name:
Currently the package name for the classes generated from Pkl modules (when using the Gradle plugin or the CLI) is always derived from the module name defined within the Pkl module file:
This is, however, not very flexible, because there are use cases when the module name's prefix and the desired Java/Kotlin package name may differ. For example, when publishing Pkl packages (with
PklProject
) it is expected that the module name prefix matches the Pkl package name:However, if a project already uses some particular JVM package name, it would be necessary either to change the Pkl package name:
which is often inconvenient, or to live with the fact that Java classes will have different package names.
It would be nice if there was an option to override the generated classes' package name via a CLI argument or via a Gradle configuration option:
The text was updated successfully, but these errors were encountered: