compose-jb

Commit Graph

Author	SHA1	Message	Date
Oleksandr Karpovich	0b429b6ac9	Update all versions for 1.3.1 + update Changelog (#2856 ) * Add changes for 1.3.1 + update Changelog Versions: compose 1.3.1 kotlin 1.8.10 compiler: 1.4.2 * revert version update in experimental examples * Update CHANGELOG.md	2 years ago
Oleksandr Karpovich	bc6d42ef44	Update versions: compose - 1.3.0 and kotlin - 1.8.0 (#2651 ) * Update versions in examples * Add more scripts to validate example on android and k/js * Add validateExamplesIos.sh * Update CHANGELOG.md for 1.3.0 * check examples with 1.3.0-rc06 * Update the versions: compose-multiplatform - 1.3.0, kotlin - 1.8.0 * Update ComposeCompilerCompatibility (1.4.0) * Update web/yarn.lock	2 years ago
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
Igor Demin	63846c63c0	Compose 1.2.1 (#2453 )	2 years ago
Igor Demin	4ee708c598	Upgrade examples to Compose 1.2.0	2 years ago
Igor Demin	37e33fba29	Compose 1.2.0-rc02	2 years ago
Igor Demin	7ad4492f43	Migrate to 1.2.0-rc01 (#2382 )	2 years ago
Igor Demin	5d67a73f80	Update Kotlin version	2 years ago
Igor Demin	9fa322a3ee	Upgrade to 1.2.0-beta02	2 years ago
Igor Demin	a208ecba73	Upgrade to 1.2.0-beta01	2 years ago
Igor Demin	15f8b0bbd3	Revert Kotlin to 1.6.10 Version of Kotlin should be compatible with Compose that is set in gradle.properties	3 years ago
Oleksandr Karpovich	e69ac23dbf	Move compose + use kotlin 1.6.21 (#2025 ) * Move compose * Update kotlin version to 1.6.20 * Move compose + Update kotlin version to 1.6.21 * Move compose to include a fix for compose plugin (kjs specific) Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>	3 years ago
Nikolay Igotti	4af260d36a	Move to 1.1.0 (#1882 ) Co-authored-by: Roman Sedaikin <roman.sedaikin@jetbrains.com> Co-authored-by: Igor Demin <igordmn@gmail.com>	3 years ago
Alexey Tsvetkov	d23806a3f4	Update examples (#1740 ) * Update examples to Gradle 7.3.3 Resolves #1654 * Update compose and agp in examples Resolves #1117 * Fix gradle plugins classloading in examples and templates * Make falling balls mpp compatible with examples checker	3 years ago
Oleksandr Karpovich	e902beeece	release 1.0.1-rc2 with 1.6.10 (#1590 ) * move to kotlin 1.6.10-RC and corresponding compose commit * Update path to the karma plugin we are patching * Add ExperimentalComposeWebStyleApi what worries me that this actually shows that there are some cases where without any changes apart version compiler people will have to worry about such annotations * update kotlin version in templates to adopt 1.6.10-RC * web: move ComposableWithNullableTypeParameter.kt to passing test cases * update kotlin version in other places * update imageviewer example: add OptIn for experimental API * move compose * move to kotlin 1.6.10 and corresponding compose * move to kotlin 1.6.10 and corresponding compose * move to 1.0.1-rc2 * move to 1.0.1-rc2 (todoapp) Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com> Co-authored-by: Shagen Ogandzhanian <shagen.ogandzhanian@jetbrains.com>	3 years ago
Igor Demin	dbd0a21949	Modify replace.sh for replacing Compose version (#1511 ) Remove: ``` __LATEST_COMPOSE_RELEASE_VERSION__ __KOTLIN_COMPOSE_VERSION__ System.getenv("COMPOSE_TEMPLATE_COMPOSE_VERSION") ``` They pollute templates/examples. Now, all paths where we need to change the version are hardcoded in the script. Usage: ``` ./replace.sh 1.0.0-rc6 ``` This script is planned to run on CI In the future I will add support for changing Kotlin version	3 years ago
Igor Demin	f63d1ce6b8	App templates	4 years ago

17 Commits (ee77fda184a3bb561128239abb00cf8568c789cc)