Strip JST-Injected Enum Extensions

[lukebemish]

Companion to neoforged/JavaSourceTransformer#62. To ensure that the same ordering is used between production and development, no matter if enum entries come from JST or are added at runtime (or a combination, with duplicates), all JST-added enum entries are stripped at runtime, before runtime-added entries are added. The corresponding JST PR allows configuration of an annotation to add to injected entries -- in this case, @ExtensionEnumEntry.

It should be possible to backport this.

[neoforged-pr-publishing]

• Publish PR to GitHub Packages

Last commit published: 0080d08feeb79d38654301f22cd13760605cdb04 - version: 11.0.18-pr-412-strip-jst-injected-enum-entries

PR Publishing

The artifacts published by this PR:

• 📦 net.neoforged.fancymodloader:earlydisplay:11.0.18-pr-412-strip-jst-injected-enum-entries
• 📦 net.neoforged.fancymodloader:junit-fml:11.0.18-pr-412-strip-jst-injected-enum-entries
• 📦 net.neoforged.fancymodloader:loader:11.0.18-pr-412-strip-jst-injected-enum-entries

Repository Declaration

In order to use the artifacts published by the PR, add the following repository to your buildscript:

repositories {
    maven {
        name = "Maven for PR #412" // https://github.com/neoforged/FancyModLoader/pull/412
        url = uri("https://prmaven.neoforged.net/FancyModLoader/pr412")
        content {
            includeModule("net.neoforged.fancymodloader", "earlydisplay")
            includeModule("net.neoforged.fancymodloader", "junit-fml")
            includeModule("net.neoforged.fancymodloader", "loader")
        }
    }
}