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.

Sign up for GitHub

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

Jump to bottom

Gradle Plugin Portal still shows 1.4.30 as the latest version for Dokka Gradle plugin #1918

Closed
izeye opened this issue May 13, 2021 · 3 comments
Closed

Gradle Plugin Portal still shows 1.4.30 as the latest version for Dokka Gradle plugin #1918

izeye opened this issue May 13, 2021 · 3 comments
Labels
infrastructure Everything related to builds tools, CI configurations and project tooling

Comments

@izeye
Copy link

izeye commented May 13, 2021

Dokka Gradle plugin 1.4.32 is available, but Gradle Plugin Portal still shows 1.4.30 as the latest version for Dokka Gradle plugin somehow.

See https://plugins.gradle.org/plugin/org.jetbrains.dokka
@MarcinAman MarcinAman added the infrastructure Everything related to builds tools, CI configurations and project tooling label May 19, 2021
@MarcinAman
Copy link
Contributor

We are present primarily on mavenCentral, but i don't see a reason not to publish artefacts to gradle plugin portal. The version that you see was a work-around but we can continue to publish there.

As this is not crucial i'll do it within a few days

@sschuberth
Copy link

sschuberth commented Nov 17, 2021 •
edited
Loading

As this is not crucial i'll do it within a few days

It is somewhat crucial to publish to the Gradle plugin portal, as when using the recommended plugin DSL to apply plugins, Maven Central is not searched by default, and user must manually configure it as a custom repository, which is quite inconvenient.

@vmishenev
Copy link
Member

We have published Dokka 1.6.0 (the latest version at this moment) on the Gradle plugin portal. Next versions will be presented there as well.

@vmishenev vmishenev mentioned this issue Jan 12, 2022
Closed
vmishenev added a commit that referenced this issue May 12, 2023
@vmishenev
Eliminate unneeded LimitedDispatcher instances on `Dispatchers.Defa…
999b5a1 
…ult` and `Dispatchers.IO` (#3562)

* Handle `Dispatchers.IO.limitedParallelism(Int.MAX_VALUE)` case

`LimitedDispatcher.limitedParallelism` returns `this` if requested parallelism is greater or equal
to the own parallelism of the said `LimitedDispatcher`. `UnlimitedIoScheduler` has parallelism effectively set
to `Int.MAX_VALUE`, so `parallelism >= this.parallelism` check folds into `parallelism == Int.MAX_VALUE`.

Before the change `LimitedDispatcher(Int.MAX_VALUE)` was returned. While it does work as expected, any submitted task
goes through its queue and `Int.MAX_VALUE` number of workers. The change allows eliminating the `LimitedDispatcher`
instance and its queue in this extreme case.

* Handle `Dispatchers.Default.limitedParallelism` when requested parallelism >= core pool size (#3442)

`LimitedDispatcher.limitedParallelism` returns `this` if requested parallelism is greater or equal
to the own parallelism of the said `LimitedDispatcher`. `DefaultScheduler` has parallelism effectively set
to `CORE_POOL_SIZE`.

Before the change `LimitedDispatcher(parallelism)` was returned. While it does work as expected, any submitted task
goes through its queue and `parallelism` number of workers. The change allows eliminating the `LimitedDispatcher`
instance and its queue in case the requested parallelism is greater or equal to `CORE_POOL_SIZE`.

Fixes #3442
Added benchmarks on cacheable child serializers

Relates #1918
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
infrastructure Everything related to builds tools, CI configurations and project tooling
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@sschuberth @izeye @vmishenev @MarcinAman