This plugin is broken due to https://s01.oss.sonatype.org being decommissioned

[pearj]

When trying to start intellij, I've noticed that the vineflower plugin is complaining that it can't download vineflower:

2026-02-19 16:21:23,106 [  45599] SEVERE - #org.vineflower.ijplugin.VineflowerState - Failed to download Vineflower
java.util.concurrent.CompletionException: java.io.IOException: Server returned HTTP response code: 402 for URL: https://s01.oss.sonatype.org/service/local/repositories/releases/content/org/vineflower/vineflower/maven-metadata.xml
	at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:332)
	at java.base/java.util.concurrent.CompletableFuture.uniComposeStage(CompletableFuture.java:1177)
	at java.base/java.util.concurrent.CompletableFuture.thenCompose(CompletableFuture.java:2309)
	at org.vineflower.ijplugin.VineflowerState.downloadVineflower(VineflowerState.kt:148)
	at org.vineflower.ijplugin.VineflowerState.initialize(VineflowerState.kt:84)
	at org.vineflower.ijplugin.VineflowerPreloader.appFrameCreated(VineflowerPreloader.kt:7)

So I went to the https://s01.oss.sonatype.org/service/local/repositories/releases/content/org/vineflower/vineflower/maven-metadata.xml and it complains about a license problem.

I went to the base of the URL, https://s01.oss.sonatype.org/ and it is asking for a trial license to be installed, after a bit of digging I found out that it is the Nexus 2 product version 2.15.2-03. That product is already EOL, so it made be wonder if https://s01.oss.sonatype.org/ is defunct too, and I came across: https://central.sonatype.org/pages/ossrh-eol/. It turns out https://s01.oss.sonatype.org/ is EOL since June 30, 2025, I guess it finally started breaking just now.

Possibly we just need to replace:

https://s01.oss.sonatype.org/service/local/repositories/releases/content/org/vineflower/vineflower/maven-metadata.xml with https://repo1.maven.org/maven2/org/vineflower/vineflower/maven-metadata.xml (from regular maven central).

[pearj]

I emailed central support and asked about the s01 url and they said:

You have asked about the legacy OSSRH service. That service was sunset on June 30th, 2025 due to the retirement of the underlying Sonatype Nexus Repository Manager 2 application. All existing publishers have been migrated to the Central Publisher Portal (https://central.sonatype.com/). Publishers should be able to log in via their username/password accounts that they previously used to log in via an OSSRH server. From there, they should see all of their namespaces. If there are any related to your account that you do not see, please let us know and we will work with you to ensure you retain publishing access. Your patience is appreciated as we anticipate a higher than usual support load.

If you published via OSSRH, you will need to update your publishing process to accommodate the new Publisher Portal. If it meets your use-case, the fastest way to continue publishing would be to use the OSSRH Staging API Service (a compatibility service that translates a subset of the Nexus 2 APIs to the Portal API). If you choose this route, you will need to generate a Portal user token to replace your OSSRH user token, point your plugin at the new service's URL, and potentially add calls to manual endpoints to your build if you are using a "Maven-like" API (e.g. Gradle's default maven-publish plugin). The documentation linked previously should provide more information, but please let us know if you encounter any issues.

If you prefer to jump right to publishing via the Portal directly, we support publishing via a Maven plugin, uploading a bundle, or calling the API directly. Additionally, we have a number of third-party Gradle plugins that we do not support ourselves, but recommend users check out.

[aoqia194]

To whoever in the future looks into this more, I'd recommend JReleaser if using Gradle. It has served me well for migration to the new central.

[zml2008]

@pearj please don't harrass sonatype support for no reason, every OSSRH publisher already got an email with the details you commented

@aoqia194 VF has already been updated to publish to the new endpoint, we have no interest in additional external tools

[pearj]

please don't harrass sonatype support for no reason, every OSSRH publisher already got an email with the details you commented

@zml2008 when I sent the message to sonatype support I hadn't yet discovered that OSSRH service was decommissioned, I merely thought it was an outage and was reporting it to them.

VF has already been updated to publish to the new endpoint

While Vineflower itself is fine, this intellij plugin is not, because it still points to the decommissioned https://s01.oss.sonatype.org URLs as seen here:

vineflower-intellij/src/main/kotlin/org/vineflower/ijplugin/VineflowerState.kt

Lines 48 to 50 in d1d3901

	var newReleaseBaseUrl: String = "https://s01.oss.sonatype.org/service/local/repositories/releases/content/org/vineflower/vineflower/"
	@JvmField
	var newSnapshotsBaseUrl: String = "https://s01.oss.sonatype.org/service/local/repositories/snapshots/content/org/vineflower/vineflower/"

I've just added a PR that fixes it (#39), I built the plugin for myself last night and it made the plugin work again.