Dev environment and mixin tweaker + mod in one jar doesn't work in yet another case

[Barteks2x]

Issue looks similar to #207.

This time, when a mod that has a mixin, coremod and a normal forge mod in one jar is added as a standard compile or runtime dependency, mod mod won't get loaded. The same jar file is loaded when added as deobfCompile dependency, but what I want is a runtime dependency, not compile.

MANIFEST.MF contains:

Manifest-Version: 1.0
TweakOrder: 0
FMLCorePluginContainsFMLMod: true
FMLAT: cubicchunks_at.cfg
TweakClass: org.spongepowered.asm.launch.MixinTweaker
ForceLoadAsMod: true
FMLCorePlugin: io.github.opencubicchunks.cubicchunks.core.asm.coremod.
 CubicChunksCoreMod

[Mumfrey]

Most likely a fault in the convoluted injection logic of FML agent again, too hacky for its own good. I'll look into it when I have a moment.

[TerminatorNL]

I too ran into this problem, but you can use deobfProvided as quick workaround. if you do that, you'll lose comments when browsing through your code, and it messes with the variable names.

But at runtime: it works like a charm.

[Barteks2x]

deobfProvided is the exact opposite of what I need. Provided dependencies are used at compile time but not added to class path at runtime. I want something is on the classpath at runtime but that I don't have access to when compiling. It's way too easy to accidentally use some implementation detail from the implementation jar.

[TerminatorNL]

If you don't need it in your IDE... Can't you just add the jars to the mods/library folder? I might be missing your point here though.

[Barteks2x]

The point is that it should just work without messing around in IDE settings every single time I refresh gradle project. ForgeGradle also has runClient and runServer tasks that won't really work without adding a runtime dependency there.