Not sure if Gradle is place to ask, but testing. I...

# gradle

[Joel Denke]

Not sure if Gradle is place to ask, but testing. If I want to have faster downloads from like maven repos, can I do something in Gradle? So annoying have very fast SSD disk and 1 Gigabit and cant use the power of bandwidth and wait forever to re-sync when updating libs.
Like fetch everything in parallell and remove bottlenecks in servers used.

[Vampire]

If you look at the channel and server topics, you find that it is not the place to ask, as your question is in no way Kotlin related. There you also find alternative places to ask. 😉

[Joel Denke]

Well depends how you see it, using Gradle Kotlin DSL to define repos. Its part of the Kotlin sync process. But this feels very odd I am not allowed ask this.
Please tell me which Slack to use, thats not using "Not Kotlin" emojis for grey zone topics.

[jpg]

Heh, you are allowed but you might not find the advice you need.
In this case I would join and ask on the Gradle Slack, you can find the invite link here: https://gradle.org/help/

[jpg]

Generally speaking this channel is mostly used for Kotlin specific stuff, either Kotlin DSL or Kotlin Plugin questions.

[Joel Denke]

I soon feel I should create my own programming.slack.com where youre allowed ask anything about programming 😛
I am member in a lot of Slack servers, but gets really fragmented and rediciolous I cant ask this questions here.
To me this is Kotlin specific, as using Gradle + Kotlin.

[Vampire]

Just because you use Kotlin, the question is not Kotlin specific. It is a a generic Gradle question. And as I said, the topic makes it pretty clear that those questions are off-topic here and where to ask instead. 😉

[Vampire]

It's not my rules, I'm just trying to following them. If you don't like the rule, feel free to discuss it (yet another time) in #meta. 🙂

[Joel Denke]

Yeah will do, thanks 🙂

[eygraber]

I agree about this not being a Kotlin topic just because the Gradle Kotlin DSL is being used, and it should probably be discussed in the Gradle slack, UNLESS @Joel Denke issue with slow dependency downloads is related to Compose multiplatform.

In which case it's still not a Kotlin issue, but more of a slow Jetbrains Maven repo issue.

[Joel Denke]

It was primary about compose multiplatform deps being slow actually. But in general as well.

[eygraber]

I find that Maven central and Google's Maven repo are typically pretty fast. Anything else can get slow, especially with KMP since it gets multiplied by the amount of targets. Compose multiplatform is particularly bad because it's multiplied by having a lot of artifacts + their repo does seem quantifiably slower

[Joel Denke]

My main issue I think is that cross dependencies between multiple repo servers. But yeah I will check and see. Thanks for input! 🙂

[Daniel B Duval]

FWIW, Kotlin or Groovy DSL aside, this isn’t an item so much solved by Gradle but one that can be helped / improved by Gradle.
E.g.,
• implement any number of the caching options that will allow for faster resolution when a the build is not clean (and avoid clean builds unless really needed).
• You could even stand up your own Gradle remote cache server and use that.
• You can look at moving to a closer neighbor for dependency housing. E.g., a locally hosted Nexus instance that acts as a proxy to maven repos for items not yet there.
• Cache configuration.
• Etc.
While the connection to/from and bandwidth for getting items isn’t going to get solved by Gradle, there are items in the build tool that will get you what you want and take advantage of the SSD that you have in place.