Fabric Loom builds erroneous binaries for maven publication
See original GitHub issueUsing the fabric example mod, I found that the default built jars are the dev jar (in yarn mappings) and the sources jar (in intermediary mappings).
I believe it’s supposed to build both jars (regular jar and sources jar) in intermediary mappings.
Steps of replication:
- Clone fabric example mod
- Run
./gradlew publishToMavenLocal
- Check
.m2/repositories/net/fabricmc/fabric-example-mod
for the built artifacts - Open both artifact (jar) with jd-gui, observe the yarn name of
MinecraftClient
in the example mixin in the dev jar and the intermediary name in the example mixin in the sources jar.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
documentation:fabric_loom [Fabric Wiki]
Loom provides utilities to install Minecraft and mods in a development environment so that you can link against them with respect to Minecraft ......
Read more >maven-publish: using loom, components.java exposes way ...
Currently, just dropping maven-publish into a fabric gradle project creates a crazed pom ... The input to maven-publish is usually components.java, and that...
Read more >How to fix "plugin was not found in any of the following sources"
In a corporate environment if custom plugins can be presented in build files then a plugin repository URL, user & pass need to...
Read more >Gradle can't find project fabric-loom-0.8_SNAPSHOT
When i try to build i get this error: Plugin [id: 'fabric-loom', version: '0.7-SNAPSHOT'] was not found in any of the following sources:....
Read more >problem with fabric-loom when building fabric mod : r/fabricmc
however the build fails with the following error: An exception occurred applying plugin request [id: 'fabric-loom', ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Is this still an issue? I didnt think it was?
I don’t think I ever experienced it after like 0.2.6, which is years ago.