Paul Merlin

@ThadHouse, see * https://github.com/gradle/gradle/issues/17659

This was fixed for Gradle 8.1 as part of * https://github.com/gradle/gradle/pull/23956 The standalone script compilation is now configured to skip the pre-release check in order to allow referencing Kotlin code...

Thanks for the report dwschulze, I've not so much free cycles theses days will take a closer look asap. In the meantime if you happen to track the problem down,...

To make it work whatever is the working directory when invoking the app I had to use: ```kotlin jvmArgs += "-splash:${'$'}APPDIR/resources/splash.png" ```

@zoff99 `APPDIR` environment variable is set by the `jpackage` launcher. The splash screen will only show up when running the application distributable, not when running using the `run` task or...

FYI Gradle 8 will do a full roundtrip on the first invocation with CC enabled. See work in progress here https://github.com/gradle/gradle/issues/21985#issuecomment-1260018610 The goal is for this to be the default...

I second this feature request. This would make it possible to use dokka in existing projects. Without it dokka forces users to restructure their build. For some projects this is...

This looks like a sensible approach to this problem! Any chance this can get some attention and be merged?

Related https://youtrack.jetbrains.com/issue/KT-54888/Add-Gradle-property-to-suppress-kotlinOptions.freeCompilerArgs-modification-on-execution-phase The warning can be suppressed using `kotlin.options.suppressFreeCompilerArgsModificationWarning=true` in `gradle.properties` Also see this comment in particular https://youtrack.jetbrains.com/issue/KT-27301/Expose-compiler-flags-via-Gradle-lazy-properties#focus=Comments-27-6565858.0-0 > All kotlinOptions and related DSL are not marked as deprecated until...

Fixed by * https://github.com/gradle/gradle/pull/23461 This will be in Gradle 8.1