Finally decided to update to the latest Forge for 1.8 and have hit a snag: I can no longer successfully compile the mod. It seems some things have changed with Gradle, e.g. including a 'task sourceJar' in the build.gradle results in a failure due to it already existing, whereas it didn't before.

 

Anyway, here is my error message:

Execution failed for task ':retromapReplacedMain'.
> filename net\minecraft\entity\DirtyEntityAccessor.java found package net\minecraft\entity->net/minecraft/entity but no class map for null

I'm not sure if the forward- vs. back-slashes is significant - I am on a Windows machine.

 

I've tried changing various things in my build.gradle and running gradlew clean to no avail.

 

Here is the original build.gradle that works (on a VERY outdated version of Forge...), and here is the new one that is not working:

 

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:2.0-SNAPSHOT'
}
}

apply plugin: 'net.minecraftforge.gradle.forge'

version = "2.1"
group= "com.google.coolalias008.dynamicswordskills" 
archivesBaseName = "1.8-dynamicswordskills"

minecraft {
version = "1.8-11.14.4.1563"
runDir = "eclipse"
mappings = "snapshot_nodoc_20150712"
}

dependencies {
//compile files (
//	"eclipse/mods/1.7.10-Battlegear-Bin-1.0.6.2.jar"
//)
}

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'
}
}

 

Any ideas?

This also happens with the recommended 1.8.9 Forge build 1722, even after removing the offending class from the build path. Deleting that package entirely allows the project to build.

 

Has the Forge team decided to explicitly disallow creating a class with a vanilla Minecraft package declaration, or is this a bug? I hope it's a bug, as it's really handy to access protected methods and fields and has worked great up until now.

 

Yes, I know I can 'just use Reflection', but it's much more fun this way

 

EDIT: Btw, the code still works fine while running in Eclipse - it just doesn't want to play nice at compile time.