https://kotlinlang.org
Join Slack
2.1.20 forbids the usage of the `application` plugin but its replacement in KMP modules, `jvm.binar...
# gradle
c
2.1.20 forbids the usage of the 
application
plugin but its replacement in KMP modules, 
jvm.binaries.executable
is marked as experimental and unstable… I'd be nice if the alternatives were stabilized before removing the old way
c
Starting with Gradle 8.7, the Application plugin is no longer compatible with the Kotlin Multiplatform Gradle plugin. Kotlin 2.1.20 introduces an Experimental DSL to achieve similar functionality. The new 
executable {}
block configures execution tasks and Gradle distributions for JVM targets.
you could be happy to have an replacement, even if it’s experimental, I guess.
c
I know, but that was a warning, which is fair. Still, deleting a thing before its replacement is ready isn't great.
c
WDYM with deleteing. just add the 
application
plugin yourself if you need it and are not using gradle 8.7+
c
With Kotlin 2.1.20, using 
application
doesn't compile anymore
Before 2.1.20, it was a warning
t
you should still be able to use 
application
plugin in projects with Gradle <8.7
☝🏼 1
c
Yeah, but if I downgrade Gradle everything else breaks
t
regarding DSL - it is a little strange to release something new without going through stabilitzation period
so far it looks like no major changes will be done on this DSL
c
Sure, I'm not saying there shouldn't be a stabilization period. i'm saying using 
application
shouldn't become an error until after the stabilization period ends.
☝️ 1
t
unfortunately we need to be compatible with Gradle deprecations and upcoming Gradle 9.0 release where such combination will not work even if we will not prohibit it
😕 1
v
You can also easily achieve the same the 
application
plugin does in KMP projects using the 
distribution
plugin directly. 🤷‍♂️
10 Views
Open in Slack
PreviousNext
Powered by

kotlinlang

A modern programming language that makes developers happier.

Powered by