Merge compose.desktop.application plugin with compose plugin
This change removes `org.jetbrains.compose.desktop.application` plugin id
in favor of doing everything in `org.jetbrains.compose`.
The change simplifies configuring Compose Desktop projects.
Now, just one plugin dependency is needed.
To avoid task name conflicts with common task names such as `package` and `run`,
the plugin creates tasks lazily only if `application` block/property is used in a script.
@ -53,6 +51,8 @@ Tasks that are not compatible with the current OS are skipped by default.
@@ -53,6 +51,8 @@ Tasks that are not compatible with the current OS are skipped by default.
aggregating all package tasks for an application.
* `run` is used to run an app locally. You need to define a `mainClass` — an fq-name of a class,
containing the `main` function.
Note, that the tasks are created only if the `application` block/property is used in a script.
After a build, output binaries can be found in `${project.buildDir}/compose/binaries`.
@ -144,7 +144,7 @@ If the default configuration is ambiguous or not sufficient, the plugin can be c
@@ -144,7 +144,7 @@ If the default configuration is ambiguous or not sufficient, the plugin can be c
```kotlin
plugins {
kotlin("jvm")
id("org.jetbrains.compose.desktop.application")
id("org.jetbrains.compose")
}
val customSourceSet = sourceSets.create("customSourceSet")