Switch Gradle tasks to use javaexec #295

Closed
opened 2025-12-30 01:23:15 +01:00 by adam · 1 comment
Owner

Originally created by @bioball on GitHub (Mar 3, 2025).

Truffle as of 0.24.1 uses native bindings for an optimized runtime. However, binding to a C library within a plugin is fraught; Pkl Gradle should ideally be using javaexec to call into Pkl to avoid any issues.

Originally created by @bioball on GitHub (Mar 3, 2025). Truffle as of 0.24.1 uses native bindings for an optimized runtime. However, binding to a C library within a plugin is fraught; Pkl Gradle should ideally be using `javaexec` to call into Pkl to avoid any issues.
adam closed this issue 2025-12-30 01:23:15 +01:00
Author
Owner

@bioball commented on GitHub (Mar 6, 2025):

I have a WIP branch here: https://github.com/bioball/pkl/tree/gradle-javaexec

I actually think we should not do this. It adds at least a second overhead to every Pkl task. This is a lot, especially for things like the synthesized analyze imports task, which is an implicit task of every "normal" task.

Closing this.

@bioball commented on GitHub (Mar 6, 2025): I have a WIP branch here: https://github.com/bioball/pkl/tree/gradle-javaexec I actually think we should not do this. It adds at least a second overhead to every Pkl task. This is a lot, especially for things like the synthesized analyze imports task, which is an implicit task of every "normal" task. Closing this.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/pkl#295