compose-jb

377 Tags

355 MiB

Tree: c5b624713e

Author	SHA1	Message	Date
Nikita Lipsky	c5b624713e	Restructure benchmarks folders (#3157 ) - move benchmarks content to benchmarks/desktop, benchmarks-intellij to benchmarks/intellij	2 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
Alexey Tsvetkov	8c8b4147ab	Update to 0.4.0-build182 and get rid of jcenter The build `0.4.0-build182` upgrades `kotlinx-collections-immutable` library (which is used by the compose runtime) to 0.3.4, which was published to maven central, so most usages of sunsetting jcenter repo can be removed now. Resolves #557	4 years ago
Nikolay Igotti	84163e7499	Move to 0.2.0-build132	4 years ago
Nikolay Igotti	18afa24fe0	Move to 0.2.0-build128	4 years ago
Alexey Tsvetkov	c105e3a8eb	Change marker comment for Compose version The verb `update` in `__UPDATE_COMPOSE_VERSION_MARKER__` could be read as an instruction to update the plugin, which might be confusing for users. I suggest renaming the marker to more neutral `__LATEST_COMPOSE_RELEASE_VERSION__`	4 years ago
Andrew Rudenko	60ac4a7ab1	initialize benchmarks (#77 )	4 years ago