Jump to content

SquidDev

Members
  • Posts

    2
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

SquidDev's Achievements

Tree Puncher

Tree Puncher (2/8)

0

Reputation

  1. If anyone else has this problem I've found a solution similar to this: Adding this to build.gradle configurations { fatPackage } sourceSets.main.compileClasspath += [configurations.fatPackage] jar { from configurations.fatPackage .findAll { it.getAbsolutePath().contains("org.squiddev") } .collect { it.isDirectory() ? it : zipTree(it) } } and putting my dependencies under fatPackage instead of compile resolves it. Its slightly hacky but everything seems to work.
  2. I've been trying to package several Maven dependencies into the released Jar file. On a normal Gradle instance I can add: jar { from configurations.compile .findAll { it.getAbsolutePath().contains("org.squiddev") } .collect { it.isDirectory() ? it : zipTree(it) } } And it will package all dependencies in the group org.squiddev.* into the produced Jar file. However when using ForgeGradle all Minecraft/Forge dependencies (net.minecraft, cpw.mods.fml) seem to get lost and it cannot compile. My build.gradle and the log are on this gist. I'm just wondering what I'm doing wrong?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.