compose-jb

Tree: d2a915a86f

Igor Demin 83b9768859 Don't publish `build-helpers`, use it directly Fixes https://youtrack.jetbrains.com/issue/CMP-1339/Change-description-of-androidx-artifacts-in-Maven-Central-stage We need some changes in it: https://youtrack.jetbrains.com/issue/CMP-7198/Maven-Central-publication-publishes-old-artifacts-for-Core-Bundle https://youtrack.jetbrains.com/issue/CMP-1339/Change-description-of-androidx-artifacts-in-Maven-Central-stage and the current workflow is complicated: - make changes - publish this as a library in the dev repo - add this as a dependency in some Gradle project (Example `2d8c5f479f/mpp/build.gradle.kts (L286)`) - Run the gradle task on CI from compose-multiplatform-core project ``` clone compose-multiplatform-core ./gradlew reuploadArtifactsToMavenCentral --info --stacktrace -Pmaven.central.sign=true -Pmaven.central.group=$group -Pmaven.central.stage=$stage -Pmaven.central.version=$version -Pmaven.central.staging.close.after.upload=true ``` This task also doesn't use any of `compose-multiplatform-core` info, so it is overhead to store it as part of this project. Now we just change some code, and it is already can be run by CI. Related change on CI: `14790a5068` Related change in core: TODO ## Testing 1. Run https://teamcity.jetbrains.com/buildConfiguration/JetBrainsPublicProjects_Compose_UploadToMavenCentralManually on branch igor.demin/upload-to-maven-central-without-library with: 2. See:	1 week ago
..
gradle-wrapper.jar	Don't publish `build-helpers`, use it directly	1 week ago
gradle-wrapper.properties	Don't publish `build-helpers`, use it directly	1 week ago

Igor Demin 83b9768859 Don't publish `build-helpers`, use it directly

Fixes https://youtrack.jetbrains.com/issue/CMP-1339/Change-description-of-androidx-artifacts-in-Maven-Central-stage

We need some changes in it:
https://youtrack.jetbrains.com/issue/CMP-7198/Maven-Central-publication-publishes-old-artifacts-for-Core-Bundle
https://youtrack.jetbrains.com/issue/CMP-1339/Change-description-of-androidx-artifacts-in-Maven-Central-stage

and the current workflow is complicated:
- make changes
- publish this as a library in the dev repo
- add this as a dependency in some Gradle project (Example 2d8c5f479f/mpp/build.gradle.kts (L286))
- Run the gradle task on CI from compose-multiplatform-core project
```
clone compose-multiplatform-core
./gradlew reuploadArtifactsToMavenCentral --info --stacktrace -Pmaven.central.sign=true -Pmaven.central.group=$group -Pmaven.central.stage=$stage -Pmaven.central.version=$version -Pmaven.central.staging.close.after.upload=true
```
This task also doesn't use any of `compose-multiplatform-core` info, so it is overhead to store it as part of this project.

Now we just change some code, and it is already can be run by CI.

Related change on CI:
14790a5068

Related change in core:
TODO

## Testing
1. Run https://teamcity.jetbrains.com/buildConfiguration/JetBrainsPublicProjects_Compose_UploadToMavenCentralManually on branch igor.demin/upload-to-maven-central-without-library with:

2. See:

1 week ago

gradle-wrapper.jar Don't publish `build-helpers`, use it directly 1 week ago

gradle-wrapper.properties Don't publish `build-helpers`, use it directly 1 week ago