github
/
compose-jb
mirror of https://gitee.com/github-sync-mirror/compose-jb.git
1
0
Fork 0
Code Issues Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1510 Commits
244 Branches
378 Tags
388 MiB
Tree: e301429247
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e301429247'
${ noResults }
compose-jb/gradle-plugins/gradle.properties

18 lines
737 B
Raw Normal View History Unescape

Enable official code style when root dir is opened in Intellij
4 years ago
org.gradle.parallel=true
kotlin.code.style=official
Allow overriding COMPOSE_GRADLE_PLUGIN_COMPOSE_VERSION via Gradle property Gradle properties are more convenient for local builds
4 years ago
More CI fixes (#1649) * Update Kotlin in SplitPane component * Use skiko-awt-* artifacts instead of skiko-jvm-*
3 years ago
# __LATEST_COMPOSE_RELEASE_VERSION__
Allow customizing Compose compiler plugin (#2347) By default, the Compose Multiplatform Gradle plugin uses `org.jetbrains.compose.compiler:compiler:<COMPOSE_VERSION>` as a compiler plugin . However, a new version of Kotlin might be incompatible with the default version of compiler plugin. Previously, that forced users to update to a new version of Compose Gradle plugin & Compose libraries in order to use a new version of Kotlin. Accordingly, Compose framework developers had to release a new version of all libraries, when a new version of Kotlin is released. Some time ago the Compose team at Google made it possible to update a compiler plugin without updating the Gradle plugin and/or all Compose libraries https://developer.android.com/jetpack/androidx/releases/compose-kotlin This change allows to specify a custom compiler artifact by using the following DSL: ``` compose { kotlinCompilerPlugin.set("<VERSION<") // or kotlinCompilerPlugin.set("<GROUP_ID>:<ARTIFACT_ID>:<VERSION>") } ```
2 years ago
# Default version of Compose Libraries used by Gradle plugin
Introduce ProGuard integration for Compose/Desktop packaging (#2313) Resolves #1174
2 years ago
compose.version=1.2.0-alpha01-dev774
Allow customizing Compose compiler plugin (#2347) By default, the Compose Multiplatform Gradle plugin uses `org.jetbrains.compose.compiler:compiler:<COMPOSE_VERSION>` as a compiler plugin . However, a new version of Kotlin might be incompatible with the default version of compiler plugin. Previously, that forced users to update to a new version of Compose Gradle plugin & Compose libraries in order to use a new version of Kotlin. Accordingly, Compose framework developers had to release a new version of all libraries, when a new version of Kotlin is released. Some time ago the Compose team at Google made it possible to update a compiler plugin without updating the Gradle plugin and/or all Compose libraries https://developer.android.com/jetpack/androidx/releases/compose-kotlin This change allows to specify a custom compiler artifact by using the following DSL: ``` compose { kotlinCompilerPlugin.set("<VERSION<") // or kotlinCompilerPlugin.set("<GROUP_ID>:<ARTIFACT_ID>:<VERSION>") } ```
2 years ago
# Default version of Compose Compiler used by Gradle plugin
Use another version of Compose Compiler inside Compose Gradle plugin (#2256) * Use another version of Compose Compiler inside Compose Gradle plugin * Update gradle.properties
2 years ago
compose.compiler.version=1.3.0-alpha01
Allow customizing Compose compiler plugin (#2347) By default, the Compose Multiplatform Gradle plugin uses `org.jetbrains.compose.compiler:compiler:<COMPOSE_VERSION>` as a compiler plugin . However, a new version of Kotlin might be incompatible with the default version of compiler plugin. Previously, that forced users to update to a new version of Compose Gradle plugin & Compose libraries in order to use a new version of Kotlin. Accordingly, Compose framework developers had to release a new version of all libraries, when a new version of Kotlin is released. Some time ago the Compose team at Google made it possible to update a compiler plugin without updating the Gradle plugin and/or all Compose libraries https://developer.android.com/jetpack/androidx/releases/compose-kotlin This change allows to specify a custom compiler artifact by using the following DSL: ``` compose { kotlinCompilerPlugin.set("<VERSION<") // or kotlinCompilerPlugin.set("<GROUP_ID>:<ARTIFACT_ID>:<VERSION>") } ```
2 years ago
# Default version of Kotlin compatible with compose.compiler.version
Use another version of Compose Compiler inside Compose Gradle plugin (#2256) * Use another version of Compose Compiler inside Compose Gradle plugin * Update gradle.properties
2 years ago
compose.compiler.compatible.kotlin.version=1.7.10
Allow customizing Compose compiler plugin (#2347) By default, the Compose Multiplatform Gradle plugin uses `org.jetbrains.compose.compiler:compiler:<COMPOSE_VERSION>` as a compiler plugin . However, a new version of Kotlin might be incompatible with the default version of compiler plugin. Previously, that forced users to update to a new version of Compose Gradle plugin & Compose libraries in order to use a new version of Kotlin. Accordingly, Compose framework developers had to release a new version of all libraries, when a new version of Kotlin is released. Some time ago the Compose team at Google made it possible to update a compiler plugin without updating the Gradle plugin and/or all Compose libraries https://developer.android.com/jetpack/androidx/releases/compose-kotlin This change allows to specify a custom compiler artifact by using the following DSL: ``` compose { kotlinCompilerPlugin.set("<VERSION<") // or kotlinCompilerPlugin.set("<GROUP_ID>:<ARTIFACT_ID>:<VERSION>") } ```
2 years ago
# https://developer.android.com/jetpack/androidx/releases/compose-kotlin
compose.tests.androidx.compiler.version=1.3.1
compose.tests.androidx.compiler.compatible.kotlin.version=1.7.10
Provide default value for Compose version for Gradle plugin 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
4 years ago
# A version of Gradle plugin, that will be published,
# unless overridden by COMPOSE_GRADLE_PLUGIN_VERSION env var.
Move to 0.2.0-build128
4 years ago
deploy.version=0.1.0-SNAPSHOT