AT's in common require different mappings to AT's in forge

[ViciousBadger]

Hey, I'm trying to get some code to compile in the common set, using access transformers to access private fields and such. Compiling common works fine, but compiling forge errors out because forge apparently expects "SRG names" while the common project accepts the proper names from official mappings. So of course I go to find these special mappings and insert them into the forge accesstransformer.cfg while keeping the common accesstransformer.cfg as it is.. and lo and behold, it compiles now, but complains about duplicate resources.. this is the error message:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':forge:processResources'.
> Entry META-INF/accesstransformer.cfg is a duplicate but no duplicate handling strategy has been set. Please refer to https://docs.gradle.org/8.10/dsl/org.gradle.api.tasks.Copy.html#org.gradle.api.tasks.Copy:duplicatesStrategy for details.

I know next to nothing about gradle or groovy or any of that, so I have no idea how to actually enable a "duplicates strategy" of if this has any bad side effects. Just wanted to let you know the different mappings can cause issues..

[ViciousBadger]

I managed to fix it in my project by renaming the common access transformer file to accesstransformer-common.cfg and changing one line in build.gradle:

    // Automatically enable AccessTransformers if the file exists
    def at = file('src/main/resources/META-INF/accesstransformer-common.cfg')
    if (at.exists()) {
        accessTransformers.from(at.absolutePath)
    }

Now common and forge can have their own independent access transformer files without conflict