compose-jb

History

Igor Demin be0c1c87e1 Release 1.2.2 (#2561 ) * Compose 1.2.1-rc01 * Fix Web build for Kotlin 1.7.20 * Use 1.3.2.1-rc02 in Gradle plugin * Fix Gradle Plugin tests * Fix Gradle Plugin tests * Compose 1.2.1-rc03 * Update CHANGELOG.md * Update CHANGELOG.md * Compose Compiler 1.3.2.1 * Compose 1.2.1 * Update VERSIONING.md * Update gradle.properties * Fix custom JDK tests on Linux * Remove JVM target version override (#2515) Previously, we were setting kotlin.jvmTarget version to 1.8 if it was null or < 1.8. As an unintended consequence we were also overriding a version set by the jvmToolchain property. So while users expected the jvmToolchain property to set both jdk home & jdk target, we were quietly overriding jdk target. At the same time, Kotlin 1.7 sets the minimum target version to 1.8 anyway, so our override does not make sense with Kotlin 1.7+. This commit removes overriding altogether. Fixes #2511 * Update CHANGELOG.md * Update CHANGELOG.md * Update CHANGELOG.md * Update Compose * Update default ProGuard rules with changes from main branch * 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 # Conflicts: # gradle-plugins/gradle/wrapper/gradle-wrapper.properties 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 * Update ComposeCompilerCompatability.kt (#2557) * Update CHANGELOG.md * 1.2.2-rc01 * Update Compose * Update CHANGELOG.md * Compose 1.2.2 * Remove shared.podspec * Remove usages of deprecated Intellij APIs Co-authored-by: Alexey Tsvetkov <alexey.tsvetkov@jetbrains.com> Co-authored-by: Alexey Tsvetkov <654232+AlexeyTsvetkov@users.noreply.github.com>		2 years ago
..
benchmark-core	Enable warning as errors by default in web (#1803 )	3 years ago
buildSrc	Update kotlin version in web (1.7.10 -> 1.7.20)	2 years ago
compose-compiler-integration	Rename COMPOSE_CORE_VERSION and COMPOSE_WEB_VERSION to compose.version (#2365 )	2 years ago
core	Add support for transition in CSS api. (#2228 )	2 years ago
gradle/wrapper	Switch main components build to Gradle 7.3.3 (#1643 )	3 years ago
integration-core	Update kotlin version in web (1.7.10 -> 1.7.20)	2 years ago
internal-web-core-runtime	Move renderComposable to internal-web-core-runtime (#1789 )	3 years ago
kotlin-js-store	Update kotlin version in web (1.7.10 -> 1.7.20)	2 years ago
licenses/third_party	Remove license for cssom since we are not using it anymore	4 years ago
svg	Fix Compile Error (#2302 )	2 years ago
test-utils	web: pass kotlin.version property (#2044 )	3 years ago
CHANGELOG.md	Update web examples after releasing 0.5.0-build228	4 years ago
README.md	Add posibility to install missing chrome drivers for local development	4 years ago
build.gradle.kts	Compose 1.2.1 (#2453 )	2 years ago
gradle.properties	Release 1.2.2 (#2561 )	2 years ago
gradlew	Add web-core benchmarks with reports to TeamCity (#724 )	4 years ago
gradlew.bat	Build web with gradle@7.1.1 and web-landing example	3 years ago
settings.gradle.kts	Rename COMPOSE_CORE_VERSION and COMPOSE_WEB_VERSION to compose.version (#2365 )	2 years ago

README.md

Prerequisites for running Selenium tests

As of now Selenium tests are turned on by default. The minimal requirement for running this tests is to have Chrome and chromedriver installed on your machine. Currently, we don't install Chrome via gradle scripts, so if you are running tests locally make sure you have Chrome installed.

For installing chrome driver just run following command:

./gradlew installWebDrivers