Posted November 13, 20159 yr Hi When I try to use gradle build, it gives me this error: "java.util.zip.ZipException: duplicate entry: mcmod.info" I decided to check if there was an actual duplicate in the build jar, and there was. I checked some more, and found all the files were duplicated. So I removed the build.gradle, and got the error on another file. We have recently updated to the latest forge, this might be the problem but I'm not sure. Here is the build.gradle: "buildscript { repositories { maven { url "https://plugins.gradle.org/m2/" } } dependencies { classpath "gradle.plugin.net.minecraftforge.gradle:ForgeGradle:2.0.2" } } apply plugin: "net.minecraftforge.gradle.forge" version = "2.0.0-pre" group = "net.timeless.jurassicraft" archivesBaseName = "JurassiCraft" sourceCompatibility = targetCompatibility = "1.7" minecraft { version = "11.14.3.1552" runDir = "minecraft" replace '${version}', project.version mappings = "snapshot_20151107" } processResources { inputs.property "version", project.version inputs.property "mcversion", project.minecraft.version from(sourceSets.main.resources.srcDirs) { include 'mcmod.info' expand 'version': project.version, 'mcversion': project.minecraft.version } from(sourceSets.main.resources.srcDirs) { exclude 'mcmod.info' } } sourceSets { main { output.resourcesDir = output.classesDir } }"
November 15, 20159 yr Author I have tried to use the default mappings, clear cache and remove the IntelliJ resources fix, the problem still persists.
January 8, 20169 yr Any fix yet? I'm experiencing this as well. I think it probably has something to do with my updating stuff to the new version of 1.8 MDK
January 13, 20169 yr Anyone else know how to fix this? I did it once but it's doing it again and I'm not sure whats going wrong
February 18, 20169 yr I too am having issues with this, only it's not just my mcmod.info file that gradle is complaining about. For now I've found that downgrading seems to work, but then of course I cannot develop for the most recent releases. This issue really is irritating.
February 19, 20169 yr So far the best bet is to clean out your gradle project and rebuild it.. I just took my source and other files I needed out of the project folder, threw it all in the trash, and started with a fresh MDK folder.
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.