compose-jb

Commit Graph

Author	SHA1	Message	Date
Konstantin	5e6021212d	[gradle] Support new AGP with androidLibrary target (#5157 ) Since AGP `8.8.0-alpha08` there was added support generated assets in the new `androidLibrary` target. We have to support a new target configuration and work with compose multiplatform resources Fixes https://youtrack.jetbrains.com/issue/CMP-6982 ## Testing - Added gradle tests ## Release Notes ### Features - Gradle Plugin - Support compose resources in `androidLibrary` target	2 months ago
Oleksandr Karpovich	4e6f4ce850	Update actions/upload-artifact to v3 (#5135 ) According to https://github.blog/changelog/2024-02-13-deprecation-notice-v1-and-v2-of-the-artifact-actions/ v2 is deprecated. Besides that the workflow doesn't work with v2 anoymore - https://github.com/JetBrains/compose-multiplatform/actions/runs/10794252433/job/29978381803?pr=5134 : > Error: This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v2`. Learn more: https://github.blog/changelog/2024-02-13-deprecation-notice-v1-and-v2-of-the-artifact-actions/ The suggested version is v4. But it requires more changes to the workflow configuration (see https://github.com/actions/upload-artifact/issues/478). Let's use v3 for now.	3 months ago
Konstantin	c7b640348e	[gradle] Update Kotlin to 2.0 (#5043 ) Integration tests: - Kotlin -> 2.0.0 - max AGP -> 8.5.0 - max Gradle -> 8.8 Project with gradle plugins: - Kotlin -> 2.0.0 - Gradle -> 8.8	6 months ago
Igor Demin	0e38f58b42	Raise the minimal supported AGP to 8.1.0 (#4840 ) AGP 7 isn't supported by Jetpack Compose 1.7 (which we'll use in CMP 1.7) and by Lifecycle 2.8. After this CI is merged, I will: - revert the revert of [the skiko API fix](https://github.com/JetBrains/compose-multiplatform-core/pull/1328) in jb-main - raise the AGP version on TeamCity ### Details It was discovered after merging [the skiko API fix](https://github.com/JetBrains/compose-multiplatform-core/pull/1328). We had `D8: java.lang.NullPointerException` error on TeamCity. After investigating dependencies, it appears that previous the dependencies were incorrect: ``` org.jetbrains.compose.material:material -> androidx.compose.material:material:1.6.7 -> androidx.lifecycle:lifecycle-livedata-core:2.6.1 ``` And the new are correct, but aren't supported by AGP 7: ``` org.jetbrains.compose.material:material -> org.jetbrains.compose.ui -> org.jetbrains.androidx.lifecycle:lifecycle-common -> androidx.lifecycle:lifecycle-common:2.8.0 -> androidx.lifecycle:lifecycle-livedata-core:2.8.0 ``` The dependency chains was printed by this command on the `commonResources` test project: ``` ./gradlew dependencyInsight --configuration demoDebugRuntimeClasspath --dependency androidx.lifecycle:lifecycle-livedata-core ``` ## Testing 1. Create a pure Jetpack Compose project via Android Studio Hedgehog \| 2023.1.1 Patch 2 2. Set Jetpack Compose to 1.7.0-beta01 3. Downgrade AGP to 7.4.0 4. Run 5. See the error: ``` ERROR:C:\Users\igord\.gradle\caches\transforms-4\7fcc63c0892ce9266300d6463c3c751d\transformed\lifecycle-livedata-core-2.8.0-runtime.jar: D8: java.lang.NullPointerException: Cannot invoke "String.length()" because "<parameter1>" is null Execution failed for task ':app:mergeExtDexDebug'. > Could not resolve all files for configuration ':app:debugRuntimeClasspath'. > Failed to transform lifecycle-livedata-core-2.8.0.aar (androidx.lifecycle:lifecycle-livedata-core:2.8.0) to match attributes {artifactType=android-dex, asm-transformed-variant=NONE, dexing-enable-desugaring=true, dexing-enable-jacoco-instrumentation=false, dexing-is-debuggable=true, dexing-min-sdk=24, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-runtime}. > Execution failed for DexingNoClasspathTransform: C:\Users\igord\.gradle\caches\transforms-3\4aae1223695d47acd0b149bb5811ca5f\transformed\lifecycle-livedata-core-2.8.0-runtime.jar. > Error while dexing. ``` 6. Change AGP to 8.1.0 7. The run is successful. ## Release Notes ### Breaking changes - Android - Minimal supported AGP raised to 8.1.0	7 months ago
Konstantin	644c7c340b	[gradle] Add validation checks on invalid xml or item type. (#4680 ) If a project has invalid value xml files (empty/broken content or duplicated keys) then gradle will show an error. fixes https://github.com/JetBrains/compose-multiplatform/issues/4663	8 months ago
Konstantin	68dc610814	[gradle] Update gradle and AGP in test runs. (#4542 )	9 months ago
Konstantin	e9c11b0a92	Add gradle "8.6" and AGP "7.3.1", "8.2.2" to the gradle plugin integration tests (#4309 )	10 months ago
Konstantin	33482890a4	Add gradle "8.6" and AGP "7.3.1", "8.2.2" to the gradle plugin integration tests (#4309 )	10 months ago
Konstantin	2b8c35e16c	Support Res class generation in JVM only compose projects (#4183 )	11 months ago
Oleksandr.Karpovich	5d4b44eea9	Make CI run on push to the master branch Motivation: sometimes we push minor commits without a PR, but anyway sometimes they break the tests (or make something incompatible. e.g. versions update)	12 months ago
Konstantin	181bfd1612	Resources gradle plugin (#3961 )	1 year ago
Alexey Tsvetkov	3e31d9a6b0	Run Gradle test on parallel agents (#3608 )	1 year ago
Alexey Tsvetkov	9540cdcf79	Require JDK 17 for packaging (#3027 ) Previously Compose Multiplatform Gradle plugin required JDK 15+ for distribution packaging. However, fixing #2867 required always passing --mac-entitlements to jpackage, which is only available with JDK 17+.	2 years ago
Alexey Tsvetkov	382ad5b78f	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

13 Commits (6d3f5b93c41a4cfaecf9888c2368c70bf26f415e)