Skip to content

Fix ForgeGradle 7 legacy CLI setup and build - #117

Merged
KiriCattus merged 1 commit into
MinecraftModDevelopmentMods:master-1.10from
SkyBlade1978:fix/fg7-legacy-cli-build
Jul 23, 2026
Merged

Fix ForgeGradle 7 legacy CLI setup and build#117
KiriCattus merged 1 commit into
MinecraftModDevelopmentMods:master-1.10from
SkyBlade1978:fix/fg7-legacy-cli-build

Conversation

@SkyBlade1978

Copy link
Copy Markdown
Collaborator

Summary

  • run Gradle 9 / ForgeGradle 7 on a pinned Java 17 daemon while retaining the Java 8 compilation toolchain for Minecraft 1.10.2
  • add the legacy lwjgl_util compile-only dependency omitted from Mavenizer's compile classpath
  • correct mcmod.info expansion, runtime mod ID, release version, and archive naming
  • generate Eclipse launch configurations on Buildship sync and document the current CLI setup commands
  • align build and release workflows on JDK 17

Failures reproduced

  • Gradle refused to start while JAVA_HOME pointed to Java 8
  • compileJava could not access org.lwjgl.util.vector.Vector3f
  • processResources failed because mcmod.info referenced undefined description and version expansion properties

Verification

  • gradlew.bat clean build eclipse genEclipseRuns --no-daemon
  • passed in the working checkout with Java 8 still configured as JAVA_HOME; Gradle selected the Java 17 daemon from the checked-in criteria
  • passed from an isolated project copy and empty GRADLE_USER_HOME
  • produced iron-age-furniture-0.2.0.5.jar plus client/server Eclipse launch configurations

Signed-off-by: JohnBraham <johnbraham1978@outlook.com>
@KiriCattus
KiriCattus merged commit 69123c2 into MinecraftModDevelopmentMods:master-1.10 Jul 23, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants