Java 25 not supported

[NicoNekoDev]

As the title says, java 25 is not supported because of tiny-remapper.
FabricMC/tiny-remapper#162

[electronicboy]

remapping isn't a thing anymore, and paper generally expects that you run the chain with the same version of java as was used at the time, otherwise patching, etc, will generally fail anyways

[NicoNekoDev]

Is it paper that needs addressing or the devs?
Because devs will take time to adapt.

[electronicboy]

It's generally expected that if you're targeting older versions, you're using the primary supported version of Java used at that time; otherwise, platform support is shaky.

I forgot that this would impact people running against a newer version of Java than the version officially supported. Given that obfuscation is no longer a thing, however, the tooling used specifically to deal with that is likely going to see less maintenance, given how nobody really supports legacy versions. Tools like tiny-remapper are no longer critical to the projects that maintain them.

[NicoNekoDev]

Well, for myself, I'll just maintain them for my personal use. I know that obfuscation is no longer a thing, but for plugins that still adds support for older version and newer versions too, it will force them to choose to stay for longer on older versions or transition to the newer version immediately.
I even thought on how to have one obfuscated and one not obfuscated proxy that will make both 26.1+ and 1.21.11- work.
As of now, paper 26.1 is not out, but I'm already testing the support for 26.1 by upgrading to Java 25 which will be required (despite that the remap requires the same java for the targeted version).

[NicoNekoDev]

Funny enough, as of now, the fabric loader still uses tiny remapper, and it got bumped to 0.13.0.
FabricMC/fabric-loader@449eca7
Edit: just a mind thought, I believe the project will still not be obsolete. Mods that have support for multiple versions of the game will still rely on Java 25 to update to Minecraft 26.1, so they'll need the tool if they still want to support older versions of the game.

[modmuss50]

Tools like tiny-remapper are no longer critical to the projects that maintain them.

Just to be clear Tiny remapper is still fully supported, we hope to contiune to support older versions for the foreseeable future. Loom still supports using mappings on 26.1+ for those that really want to use it (not that I would recomend it though). Please make sure to report any issues you have to us.

[lynxplay]

https://docs.papermc.io/paper/dev/userdev/#adding-the-dev-bundle-dependency does this not solve it for you?
You can configure paperweight to use a specific java launcher for its tooling on older versions.

[electronicboy]

Yea, I didn't realise that it was still being used as part of the mixin stuff on fabrics side

I'm not entirely sure what our plans are, I really doubt we'll be worried about our tooling supporting remapping against bytecode where versions of the software which rely on remapping, etc, are no longer supported and can't even run that bytecode

[NicoNekoDev]

https://docs.papermc.io/paper/dev/userdev/#adding-the-dev-bundle-dependency does this not solve it for you? You can configure paperweight to use a specific java launcher for its tooling on older versions.

If I done this correctly, it should be something like this for Gradle 9, for all my sub-projects:

plugins {
    id("io.papermc.paperweight.userdev")
}

group = "com.willfp"
version = rootProject.version

dependencies {
    implementation(project(":eco-core:core-nms:common"))
    paperweight.paperDevBundle("1.21.4-R0.1-SNAPSHOT")
}

paperweight {
    javaToolchains {
        launcherFor {
            languageVersion = JavaLanguageVersion.of(21)
        }
    }
}

tasks {
    build {
        dependsOn(reobfJar)
    }

    reobfJar {
        mustRunAfter(shadowJar)
    }

    shadowJar {
        relocate(
            "com.willfp.eco.internal.spigot.proxy.common",
            "com.willfp.eco.internal.spigot.proxy.v1_21_4.common"
        )
    }
}

which seems to throw the same error.
Edit: and doing java.disableAutoTargetJvm() also throws that version 69 is not supported.

[NicoNekoDev]

I really doubt we'll be worried about our tooling supporting remapping against bytecode where versions of the software which rely on remapping, etc, are no longer supported and can't even run that bytecode

Well, that should be something the devs relying on those should be worried about. Like paperweight does support Java 24 by default, because tiny-remapper does also support it, because ASM was updated to the version that supports it, but that's not paper devs should worry about. The problem, as I've mentioned about a couple of times is that devs will need time to adjust, while they slowly drop older versions.

[jpenilla]

There is no paperweight issue here. You are able to choose the tiny remapper version used for your plugin. And if something fails in the setup pipeline it's likely user error/a bad configuration that could be fixed by reading the docs. If you need further help the Discord is more appropriate.