Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General cleanup #2809

Merged
merged 7 commits into from
Jul 8, 2021
Merged

General cleanup #2809

merged 7 commits into from
Jul 8, 2021

Conversation

qwwdfsad
Copy link
Collaborator

@qwwdfsad qwwdfsad commented Jul 6, 2021

  • Do not generate Dokka documentation for deprecated members
  • Get rid of inline classes notation
  • Opt-in into DelicateCoroutineApi in our own project
  • Get rid of JVM IR checks that are no longer relevant

reactive/kotlinx-coroutines-rx3/src/RxConvert.kt Outdated Show resolved Hide resolved
gradle/opt-in.gradle Outdated Show resolved Hide resolved
val repositoryId: String? = System.getenv("libs.repository.id")
return if (repositoryId == null) {
// Using implicitly created staging, for MPP it's likely to be a mistake because
// publication on TeamCity will create 3 independent staging repositories
System.err.println("Warning: using an implicitly created staging for coroutines")
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand the changes to this file. They don't affect anything, but still, could you explain them?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our library is multiplatform and thus should be published from multiple machines (one per supported K/N architecture).

When we're configuring publication, we have to specify the repository we're going to publish to.
The default recommended/implicitly used address is /staging/deploy/maven2/. When it's used, a new staging repository is created by the Maven plugin. Essentially it means that, when we're publishing from multiple agents, we'll create multiple staging repositories (=> multiple releases with the same version and partial artifacts set).
To avoid that, we preconfigure our builds with a pre-created staging repository and pass its id via libs.repository.id for publishing tasks.

We do not do that for regular builds, but Gradle still configures publishing tasks, so this warning has been printed as many times as we got modules on each Gradle configuration, obfuscating our build output

@qwwdfsad qwwdfsad merged commit f5e8740 into develop Jul 8, 2021
@qwwdfsad qwwdfsad deleted the cleanup branch July 8, 2021 10:47
pablobaxter pushed a commit to pablobaxter/kotlinx.coroutines that referenced this pull request Sep 14, 2022
* Suppress all deprecated signatures from the documentation
* Migrate inline classes to value
* Get rid of annoying Gradle output when tasks are configured
* Opt-in into delicate coroutines API
* Get rid of legacy jvm_ir_enabled that was used for pre-release testing of JVM IR compiler
* Update README references
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants