There are two versions used in the Gradle plugin:
* The version of the plugin itself;
* The version of Compose dependency used by the plugin.
On CI both versions are set to the same value specific to the build.
However, locally using 0.1.0-SNAPSHOT for the Compose version is inconvenient,
because we don't publish 0.1.0-SNAPSHOT anywhere.
Even if it existed, a moving version is not convenient for using in tests.
This commit changes version handling:
* The version of Compose is set via `compose.version` Gradle property
to the latest stable version, unless overridden by
`COMPOSE_GRADLE_PLUGIN_COMPOSE_VERSION` env. var.
* The version of the plugin is set via `deploy.version`
Gradle property to 0.1.0-SNAPSHOT,
unless overridden by `COMPOSE_GRADLE_PLUGIN_VERSION` env. var
The verb `update` in `__UPDATE_COMPOSE_VERSION_MARKER__`
could be read as an instruction to update the plugin,
which might be confusing for users.
I suggest renaming the marker to more neutral
`__LATEST_COMPOSE_RELEASE_VERSION__`
For some reason, the compiler failed to resolve the method reference correctly.
Also minor fix for `executable` property (the code was red in IDE, but compiled).
* Add IDE resolution warning for examples sharing JVM & Android code.
* Use Ktor to remove JVM-specific networking code from common source set
Fix resolution for Picture class via expect/actual mechanism
Co-authored-by: Sebastian Aigner <sebastian.aigner@jetbrains.com>
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.
Nikolay Igotti
Nikolay Igotti
Alexey Tsvetkov
Arkadii Ivanov
Roman Sedaikin
Igor Demin
Igor Demin
Andrew Rudenko
Malachi de AElfweald
Freek de Bruijn
Eliezer Graber
CeH9
Sebastian Aigner