Anyone else getting errors from jetbrains maven? `<https://repo.maven.apache.org/maven2/org/jetbrain...

# compose-desktop

[spierce7]

Anyone else getting errors from jetbrains maven? <https://repo.maven.apache.org/maven2/org/jetbrains/>

[jw]

All of GitHub Actions seems like it can't access all of Maven Central

[jw]

so far i see it across about 6 projects

[ephemient]

https://kotlinlang.slack.com/archives/C09222272/p1681948938672839

[ephemient]

annoyingly, it doesn't seem to be tracked by https://status.maven.org/

[ephemient]

seems like sonatype broke their DNS

[jw]

more likely that apache broke a CNAME

[ephemient]

nah the CNAME is fine: <http://repo.maven.apache.org|repo.maven.apache.org> → <http://repo.apache.maven.org|repo.apache.maven.org>. but then the authority for <http://maven.org|maven.org> responds with no address for that name

[jw]

what a convoluted mess. presumably if Gradle changes to repo1.maven.org it'll break someone's heat

[ephemient]

not like Gradle can do that without a new release anyway, and hopefully this gets resolved faster than that

[jw]

oh ya i didn't mean now. i'm sure someone suggested it in like 2012 and it was shot down because Gradle seemingly can't make anything nice

[spierce7]

Gradle seemingly can't make anything nice

I'm enjoying the new configuration cache a lot, however I still don't understand why the exact Kotlin code I compiled yesterday has to recompile again and take so long today. I don't remember that happening with Buck's cache while I was using it.

[vanshg]

for the time being locally -- s/mavenCentral()/maven("<https://repo1.maven.org/maven2>")

[CLOVIS]

Still down 🤔