compose-jb

2385 Commits

245 Branches

390 Tags

489 MiB

Tree: 71e0b05336

Commit Graph

Author SHA1 Message Date

Author	SHA1	Message	Date
Igor Demin	4ce6a59c67	Fix old version uploading to Maven Central Stage (#5185 ) Fixes https://youtrack.jetbrains.com/issue/CMP-1339/Change-description-of-androidx-artifacts-in-Maven-Central-stage Fixes https://youtrack.jetbrains.com/issue/CMP-7198/Maven-Central-publication-publishes-old-artifacts-for-Core-Bundle Related change on CI: https://jetbrains.team/p/ui/repositories/compose-teamcity-config/revision/94d34d0e Now it matches by wildcards. It doesn't fix the core issue - associating the exact library group with the exact artifacts, but fixing that requires decoupling maven central upload per project instead of comparing it by packages. It is not easy, as we not only have artifacts in compose-multiplatform-core - we have Gradle plugin, components, `compose-full`, Compose HTML. ## Testing Run CI on igor.demin/upload-to-maven-central-fixes branch Should be verified on the next 1.8.0-alpha02 release as well.	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

Igor Demin

4ce6a59c67

Fix old version uploading to Maven Central Stage (#5185 )

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

Related change on CI:

https://jetbrains.team/p/ui/repositories/compose-teamcity-config/revision/94d34d0e

Now it matches by wildcards. It doesn't fix the core issue - associating
the exact library group with the exact artifacts, but fixing that
requires decoupling maven central upload per project instead of
comparing it by packages. It is not easy, as we not only have artifacts
in compose-multiplatform-core - we have Gradle plugin, components,
`compose-full`, Compose HTML.

## Testing
Run CI on igor.demin/upload-to-maven-central-fixes branch

Should be verified on the next 1.8.0-alpha02 release as well.

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

2 Commits (71e0b05336fd732eaaf8a8e53e5a9fe453823b03)