maven-publish: using loom, components.java exposes way too many dependencies

Currently, just dropping maven-publish into a fabric gradle project creates a crazed pom with literally every dependency of minecraft, plus fabric, plus every modCompile. The input to maven-publish is usually components.java, and that is generally the only component that ever exists.

Right now there’s a workaround involving going into the xml and literally deleting the dependencies node, but this… isn’t ideal.

[NikkyAI]

you would want dependencies on other mods to go in but not loader generally… unless you jsut go ahead and include which version of fabric-loader you used as a dependency and whoever consumes the library will use that version unless they specify their own version of fabric-loader

i would also support a configuration modApi or apiMod that is modCompile and goes into the dependencies component

[Mordna]

‘api’ is basically like the old ‘compile’ meaning that any ‘api’ components (recursively) can be used/called. ‘implementation’ allows only usage of the stated library/mod without the ability to directly call/use its dependencies. This explains it way better.