github/compose-jb - compose-jb - 帆软第三方插件仓库

Author	SHA1	Message	Date
Alexey Tsvetkov	6dbe467abf	Split Maven artifact configuration and Gradle plugin configuration This is needed to introduce non-Gradle plugin modules under gradle-plugins build for Compose preview runtime.	3 years ago
Alexey Tsvetkov	938f581a3d	Update copyright notices	3 years ago
Igor Demin	64fe5bc025	Gradle plugin. Replace 'androidx.compose' artifacts by 'org.jetbrains.compose' artifacts, get version from gradle properties Fixes https://github.com/JetBrains/compose-jb/issues/272	3 years ago
Igor Demin	48b52e459a	Gradle plugin. Replace 'androidx.compose' artifacts by 'org.jetbrains.compose' artifacts. Fixes https://github.com/JetBrains/compose-jb/issues/272	3 years ago
Alexey Tsvetkov	ad0b6fc916	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
Alexey Tsvetkov	332d57ae33	Allow overriding COMPOSE_GRADLE_PLUGIN_COMPOSE_VERSION via Gradle property Gradle properties are more convenient for local builds	4 years ago
Alexey Tsvetkov	518aa7fc81	Rename JetPack -> JetBrains	4 years ago
Alexey Tsvetkov	a8e34eddad	Refactor gradle-plugin build configuration to allow other plugins So other plugins can be added to separate subprojects	4 years ago