Erik C. Thauvin

@valankar Did you ever figure it out? I'm having the same issue with `sync-to filesystem`.

You might want to talk with @Zeioth. I believe he's using the script with GitLab.

@rickyrattlesnake I'm using Gradle 7.3.3 and Kotlin 1.6.10 too, and am not seeing any warnings. The easiest way to determine if the plugin is causing the error is to comment...

Just to add closure to this issue… Our initial testing with JEP458 yielded very little benefits at this point. Some of the design decisions we made to avoid unintended side...

Hi. I'm sorry for some reason I wasn't getting notifications and completely missed your request. I'll have a look at it very shortly.

I'm really not that familiar with Kwata. Give me a bit of time to get up to speed with it, before I put my foot in my mouth.

I've looked at the [Kawa plugin for Maven](https://github.com/arvyy/kawa-maven-plugin) implementation and I don't really see anything that can't be done in bld. As you suspected, they are spawning a new process...

> > BTW, how about transferring that extension to your org? > @gbevin would have to do that.

One could write a simple extension that executes something like: ```console native-image [options] -jar jarfile [executable name] ``` Would that work for you, @YunaBraska?

You could also use the [bld-exec](https://github.com/rife2/bld-exec) extension: ```java @BuildCommand(value = "native-exec", summary = "Build a native executable") public void nativeExec() throws Exception { new ExecOperation() .fromProject(this) .command("native-image", "-jar", new File(buildDistDirectory(),...