Provide obfuscated builds on Jitpack as well
embeddedt opened this issue ยท 6 comments
Is your feature request related to a problem? Please describe.
Many mods use stable_39
mappings and cannot include a snapshot_20171003
dependency directly. The usual workaround for this is to depend on the obfuscated build and use deobfCompile
(or compile fg.deobf
) to deobfuscate to the project's own mappings. However, this doesn't seem to be available on JitPack.
Describe the solution you'd like
Add a deobf artifact to JitPack.
Describe alternatives you've considered
Depending on the build on CurseForge using CurseMaven, which is my current workaround. However, that doesn't work if I want to depend on an unreleased version.
I reimplemented the source & deobf artifacts from v1.6.2, but it seems like the stable_39 mappings don't wanna work outside the dev environment ๐
Is JitPack still broken? I can't seem to get an actual JAR out of it. https://jitpack.io/com/github/jbredwards/Fluidlogged-API/9ff5d0c/build.log only seems to list the sources JAR and nothing is downloaded when I check my Gradle cache.
As someone who isn't good with gradle, this is confusing. Jitpack.io was working at some point (probably pre v1.6.2), but I can't get it working now either. The only difference I notice is that this build.gradle uses mixin, does that perhaps have something to do with this?
@jbredwards I think #65 will fix it, just waiting for JitPack to build the PR to make sure.