MinecraftForge / ForgeGradle

Minecraft mod development framework used by Forge and FML for the gradle build system
GNU Lesser General Public License v2.1
522 stars 444 forks source link

i can't build on idea on 1.7.10 #643

Closed Mairuis closed 4 years ago

Mairuis commented 4 years ago

I m using forgegradle 1.2 on Minecraft 1.7.10. but when I click sync, it doesn't work. Minecraft doesn't have a high version of the server core, this's the only way to write mod for my server. I m going crazy, what can I do? please save my life.

S03F485UL~VCS14IEYW$U{8

build.gradle


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'

version = "1.0"
group= "com.yourname.modid" // http://maven.apache.org/guides/mini/guide-naming-conventions.html
archivesBaseName = "modid"

minecraft {
    version = "1.7.10-10.13.4.1614-1.7.10"
    runDir = "eclipse"
}

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

}

processResources
{
    // this will ensure that this task is redone when the versions change.
    inputs.property "version", project.version
    inputs.property "mcversion", project.minecraft.version

    // replace stuff in mcmod.info, nothing else
    from(sourceSets.main.resources.srcDirs) {
        include 'mcmod.info'

        // replace version and mcversion
        expand 'version':project.version, 'mcversion':project.minecraft.version
    }

    // copy everything else, thats not the mcmod.info
    from(sourceSets.main.resources.srcDirs) {
        exclude 'mcmod.info'
    }
}

`
Unnoen commented 4 years ago

We do not provide support for outdated versions. Please update.

MauveCloud commented 4 years ago

This seems to happen with newer builds of Gradle - I got the same error message with a project I'm involved with, but when I copied the gradle wrapper from an open source mod that had a branch for the 1.7.10 version of the mod, it got past that. I notice the ForgeGradle project here has a wrapper in the "FG_1.2" branch that is probably safe to use with it, but you might want to avoid performing an "Update Gradle wrapper" command on your project, which I see in the screenshot.

FinnT730 commented 4 years ago

Yeah, newer versions of FG are not supporting 1.7.10, there are many reasons why to leave that version behind.

Like Unnoen said, we do not provide support for it, even when FG breaks, even with newer versions.

jriwanek commented 4 years ago

For people who actually need a resolution, the correct answer is "Don't use gradle versions past 2.14.1 with FG1.2".

LexManos commented 4 years ago

Yes, FG is designed for a very specific version of gradle. If you use any version other then the one or mdk uses, it's at your own risk and can screw things up.