Jump to content

Recommended Posts

Posted

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?

Posted

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.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

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