Skip to content

Remapping deletes duplicate classes from jars #104

@Juuxel

Description

@Juuxel

See example project: https://github.com/Juuxel/duplicate-mods

  • There are two mod dependencies, a.jar and b.jar
    • a.jar has classes A, B
    • b.jar has classes A, B, C, D
  • When you build the project with gradlew classes, Loom will remap the mods
  • If you take a look in .gradle/loom-cache/remapped_mods, only one of the jars will have the classes A, B even though both inputs have them

This is a simplified test case from a real-life mod setup where a crossplatform mod shadows some of its modules but still depends on the other modules in its POM.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions