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.
2220 Commits
246 Branches
378 Tags
412 MiB
Tree: 705dcaf814
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '705dcaf814'
${ noResults }
compose-jb/gradle-plugins/gradle.properties

28 lines
1.2 KiB
Raw Normal View History Unescape

Enable official code style when root dir is opened in Intellij
4 years ago
org.gradle.parallel=true
Support three letters locales (#4394)
9 months ago
org.gradle.configuration-cache=true
org.gradle.caching=true
[gradle] Disable parallel tests run for gradle tests
9 months ago
org.gradle.daemon=true
Enable official code style when root dir is opened in Intellij
4 years ago
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
[gradle] Disable parallel tests run for gradle tests
9 months ago
# CI agents don't have enough resources to support it :(
dev.junit.parallel=false
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
[gradle] Update compose dependency in the gradle plugin
8 months ago
compose.version=1.6.10-dev1590
Improve DSL for setting a custom Compose Plugin (#2527) * Improve DSL for setting a custom Compose Plugin Fixes https://github.com/JetBrains/compose-jb/issues/2459 Readme: https://github.com/JetBrains/compose-jb/pull/2526 1. Add `dependencies: Dependencies` extension that is accessible in `compose { }` block 2. Add `Dependencies.compiler` property that can return versions of Compose compiler used by the plugin: ``` compose { kotlinCompilerPlugin.set(dependencies.compiler.forKotlin("1.7.20")) //kotlinCompilerPlugin.set(dependencies.compiler.auto) // determined by applied version of Kotlin. It is a default. } ``` 3. Add ability to set arguments for Compose Compiler. Now we can write: ``` compose { kotlinCompilerPlugin.set(dependencies.compiler.forKotlin("1.7.20")) kotlinCompilerPluginArgs.add("suppressKotlinVersionCompatibilityCheck=1.7.21") } ``` 4. Remove checks for different targets We had a separate check for JS, when we released 1.2.0. It doesn't support Kotlin 1.7.20 at that moment. It is hard to refactor this feature in the new code, so I removed it. It is not needed now and it had an ugly code. When we will need it again, we'll write it again. 5. Remove the `compose.tests.androidx.compiler.version` property from gradle.properties and remove `defaultAndroidxCompilerEnvironment` Because they are used only in one test, and it seems there is no reason to use it in another place in the future * Discussions
2 years ago
# The latest version of Compose Compiler used by Gradle plugin. Used only in tests/CI.
update compose compiler version to 1.5.13 (#4770)
7 months ago
compose.tests.compiler.version=1.5.13.1
Improve DSL for setting a custom Compose Plugin (#2527) * Improve DSL for setting a custom Compose Plugin Fixes https://github.com/JetBrains/compose-jb/issues/2459 Readme: https://github.com/JetBrains/compose-jb/pull/2526 1. Add `dependencies: Dependencies` extension that is accessible in `compose { }` block 2. Add `Dependencies.compiler` property that can return versions of Compose compiler used by the plugin: ``` compose { kotlinCompilerPlugin.set(dependencies.compiler.forKotlin("1.7.20")) //kotlinCompilerPlugin.set(dependencies.compiler.auto) // determined by applied version of Kotlin. It is a default. } ``` 3. Add ability to set arguments for Compose Compiler. Now we can write: ``` compose { kotlinCompilerPlugin.set(dependencies.compiler.forKotlin("1.7.20")) kotlinCompilerPluginArgs.add("suppressKotlinVersionCompatibilityCheck=1.7.21") } ``` 4. Remove checks for different targets We had a separate check for JS, when we released 1.2.0. It doesn't support Kotlin 1.7.20 at that moment. It is hard to refactor this feature in the new code, so I removed it. It is not needed now and it had an ugly code. When we will need it again, we'll write it again. 5. Remove the `compose.tests.androidx.compiler.version` property from gradle.properties and remove `defaultAndroidxCompilerEnvironment` Because they are used only in one test, and it seems there is no reason to use it in another place in the future * Discussions
2 years ago
# The latest version of Kotlin compatible with compose.tests.compiler.version. Used only in tests/CI.
update compose compiler version to 1.5.13 (#4770)
7 months ago
compose.tests.compiler.compatible.kotlin.version=1.9.24
Allow to use Compose on multiple Kotlin versions (#2366) JS target supports a lower version (1.7.10), because we have a bug in Koltin 1.7.20 Compose 1.2.0 will support: 1.7.20 and 1.7.10 for Android and Desktop 1.7.10 for JS We will release the new patchset (1.2.1) with 1.7.2X support for JS later
2 years ago
# The latest version of Kotlin compatible with compose.tests.compiler.version for JS target. Used only on CI.
update compose compiler version to 1.5.13 (#4770)
7 months ago
compose.tests.js.compiler.compatible.kotlin.version=1.9.24
Test Gradle plugin on relevant PRs (#2509) * Update Gradle used in tooling subprojects * Update Kotlin in Compose Gradle plugin * Decrease verbosity of Gradle plugin tests * Disable mac sign test * Add workflow to test Gradle plugin * Fix custom jdk tests on Linux * Make Compose Gradle plugin build compatible with Configuration cache * Print tests summary * Remove unused code * Refactor tests configuration * Turn off parallel execution * Try adding windows runner * Turn off fail fast * Fix Windows test issues #2368 * Adjust default proguard rules The following rule is needed to fix tests on Windows: ``` -dontwarn org.graalvm.compiler.core.aarch64.AArch64NodeMatchRules_MatchStatementSet* ``` Other rules are just to make builds less noisy. Kotlin's `*.internal` packages often contain bytecode, which triggers ProGuard's notes. However, these notes are not actionable for most users, so we can ignore notes by default. #2393
2 years ago
# __SUPPORTED_GRADLE_VERSIONS__
Run Gradle test on parallel agents (#3608)
1 year ago
# Don't forget to edit versions in .github/workflows/gradle-plugin.yml as well
Support multimodule projects and libraries publication with compose resources (#4454) - integrate KGP resource API - packaging final resources to iOS and JS/Wasm applications - integration tests of publication and multi module support - info logging of supported Gradle and KGP versions ### requirements - Kotlin Gradle Plugin >= 2.0.0-Beta05 - Gradle >= 7.6
9 months ago
# and Publish.Subtasks.buildTypes.gradle.GradlePluginTestKt#gradleVersions in the TC config
Add gradle "8.6" and AGP "7.3.1", "8.2.2" to the gradle plugin integration tests (#4309)
9 months ago
# minimal and current gradle version
[gradle] Update gradle and AGP in test runs. (#4542)
8 months ago
compose.tests.gradle.versions=7.4, 8.7
compose.tests.agp.versions=7.3.1, 8.3.1
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