QLoom >=1.3.1 doesnt remove transitive fabric dependencies

[SilverAndro]

if you pull in a dependency that uses fabric loader or fabric api, those dependencies are removed with qloom 1.2.3, but upgrading to 1.3.1 or later results in them not being removed, breaking running the game from the dev env

1.2.3:

1.3.1 (and later):

[TheGlitch76]

Yeah, I'm not sure what's going on here. It's the same patch as in 1.2.3

For now, you can exclude fabric deps manually:

project.configurations.all {
  exclude(group: "net.fabricmc", module: "fabric-loader")
  exclude(group: "net.fabricmc.fabric-api")
}

[KrLite]

Yeah, I'm not sure what's going on here. It's the same patch as in 1.2.3

For now, you can exclude fabric deps manually:

project.configurations.all {
  exclude(group: "net.fabricmc", module: "fabric-loader")
  exclude(group: "net.fabricmc.fabric-api")
}

Hi! I'm experiencing the same issue with quilt-loom 1.3.+. The solution you provided works, but only for Quilt-only projects, since all classes from Fabric API will be unaccessible by java, causing all the code referencing Fabric API not passing the task compileJava.

As I'm not good on groovy at all, is there any other way to fix this problem besides downgrading the Quilt Loom version? Or, when can this issue be fixed in Quilt Loom?

[AlexIIL]

So you should be able to remove the exclude(group: "net.fabricmc.fabric-api") line to make it only exclude fabric-loader - that way you can still depend on fabric api?

[KrLite]

I've tried this but this is actually causing the... duplicate of Fabric API.

But this is the closest attempt to launch.

[KrLite]

It shows that Fabric API is embedded inside the Quilted Fabric API and that's true. But in development environment, compileJava cannot recognize them, although no errors were emitted and you can still manually check these jars, existing.

[KrLite]

Now a new problem occurs, that is whatever the version of Quilt Loom I'm using, the Fabric API seems always unaccessible to the java compiler (I'm not excluding Fabric API neither excluding Fabric Loader). Is this another issue inside the Quilt toolchain? Recently with Quilt I've encountered many things I didn't used to understand...