BleuGamer

I apologize. [ { "modid": "BleuFoods", "name": "BleuFoods", "description": "Overall food preparation and cooking mod! More original name coming as end goals are realized.", "version": "${version}", "mcversion": "${mcversion}", "url": "", "updateUrl": "", "authorList": ["BleuGamer"], "credits": "", "logoFile": "", "screenshots": [], "dependencies": [] } ] buildscript { repositories { mavenCentral() maven { name = "forge" url = "http://files.minecraftforge.net/maven" } maven { name = "sonatype" url = "https://oss.sonatype.org/content/repositories/snapshots/" } } dependencies { classpath 'net.minecraftforge.gradle:ForgeGradle:1.2-SNAPSHOT' } } apply plugin: 'forge' group= "bleumods" // http://maven.apache.org/guides/mini/guide-naming-conventions.html archivesBaseName = "bleufoods" // this makes gradle recognize and use build.properties ext.configFile = file "build.properties" configFile.withReader { // Load config. It shall from now be referenced as simply config or project.config def prop = new Properties() prop.load(it) project.ext.config = new ConfigSlurper().parse prop } version = "${project.config.mod_version}." + System.getenv("BUILD_NUMBER") ?: "0" println config.mc_version + "-" + config.forge_version // Setup the forge minecraft plugin data. Specify the preferred forge/minecraft version here minecraft { version = config.mc_version + "-" + config.forge_version } dependencies { // you may put jars on which you depend on in ./libs // or you may define them like so.. //compile "some.group:artifact:version:classifier" //compile "some.group:artifact:version" // real examples //compile 'com.mod-buildcraft:buildcraft:6.0.8:dev' // adds buildcraft to the dev env //compile 'com.googlecode.efficient-java-matrix-library:ejml:0.24' // adds ejml to the dev env // for more info... // http://www.gradle.org/docs/current/userguide/artifact_dependencies_tutorial.html // http://www.gradle.org/docs/current/userguide/dependency_management.html } def root = project.projectDir.parentFile sourceSets { main { java { srcDir new File(root, "src") } resources { srcDir new File(root, "resources") } } } processResources { // this will ensure that this task is redone when the versions change. inputs.property "version", project.version inputs.property "mc_version", config.mc_version // replace stuff in mcmod.info, nothing else from(sourceSets.main.resources.srcDirs) { include '*.info' expand 'version':project.version,'mc_version':config.mc_version // replace version and mcversion expand 'version':project.version, 'mc_version':config.mc_version } // copy everything else, thats not the mcmod.info from(sourceSets.main.resources.srcDirs) { exclude 'mcmod.info' include 'assets/**/*.*' } } version = "${project.minecraft.version}-${project.version}" jar { classifier = 'universal' } task sourceJar(type: Jar) { from sourceSets.main.java from new File(rootDir, "dev") classifier = 'src' } task devJar(type: Jar) { from sourceSets.main.output classifier = 'dev' } // Tell the artifact system about our extra jars artifacts { archives sourceJar, devJar } // Configure an upload task. uploadArchives { dependsOn 'reobf' if (project.hasProperty("local_maven")) { repositories { logger.info('Publishing to local maven repo') mavenDeployer { repository(url: "file://${local_maven}") } } } } sourceSets { main { output.resourcesDir = output.classesDir } }

Thank you very much. I made the corrections in the mcmod.info file and the build was successful. Could you clarify? I am having this same issue but I can't decipher what you mean.

Comment out whatever isn't succeeding in the gradle.build and try again, especially if it's code you put in yourself or copied over.

Thank you. All is working as intended now.

This... worked.... I already have the addition to the gradle.build as what first started derailing my train was the issues with resources and intellij... I assumed running those commands inside of intellij would be sufficient.... I followed the one guys tutorial in that section, so I don't know... I'll dig a bit and see if this is a proper bug... I'm royally confuzzled... if I want to send my projects to git, will the gradle commands work? or what would be the proper way to bring gradle back into the project with minimal risk? I'm a little nervous cause it feels temperamental at the moment. Thanks for your help!

I've scoured the forums, I just know I'm doing something glaringly obvious... My last post was a facepalm but this has me seriously scratching my head. I've followed all the steps, both custom builds of my own and default...I've messed with the gradle build... I even did a clean install of windows AND linux with all defaults and still come up with the same error. It's like it's creating the mod jar file twice. This is with everything launched with factory defaults. I just extract the archive, and run the gradle build with intellij and it spits this out. I've been at this for a week, I've had some small successes but it is impossible for me to code seriously without actually being able to accomplish anything. Does anyone else have any tips? I can't be the only one this happens to when it's reproducible on a clean install.

I am an absolute idiot... the external libraries, I never thought to check because the first couple times I tried it only showed the java version... *sigh*

I did this through both the intellij gradle build and the command prompt both separately and together, and the only sorce file I ever see is the example project.

This is most likely a beaten horse, however searching and searching the forums and tutorials finds no complete/blunt answer. I have everything set up directly with idea, but is there no way to see the actual source code of forge and minecraft in 1.7.x(10)? I'm coming back into modding from the 1.4.x and 5.x days, and had all of the code for me to sift through and ponder. I've attempted decompiling and such, but it's awkward to have it so separated. is there a way? or do I have to rely on the javadocs? Or am I missing something blatantly obvious?