[7.0] Debug in Eclipse fails if using mixin

Open
#1,078 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
50/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java
Domain
build-system, developer-experience

Research direction

Reproduce the issue with the mixin MDK example using the generated Eclipse launch files, then compare that path with the working runClient Gradle task. Trace the launch configuration until the module resolution error involving mixinextras.common and MixinExtras is isolated; done means Eclipse debug and run launch successfully.

Written by the indexing model from the issue text.

Description

I'm using the mixin MDK example (it uses MC 1.21.11) and it works when using the runClient gradle task, but fails using the generated Eclipse launch files for debug or run with this error:

Exception in thread "main" java.lang.reflect.InvocationTargetException
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:118)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)
	at net.minecraftforge.bootstrap.Bootstrap.bootstrapMain(Bootstrap.java:133)
	at net.minecraftforge.bootstrap.Bootstrap.start(Bootstrap.java:53)
	at net.minecraftforge.bootstrap.ForgeBootstrap.main(ForgeBootstrap.java:19)
	at net.minecraftforge.launcher.Main$Launcher.run(Main.java:276)
	at net.minecraftforge.launcher.Main$Launcher.access$000(Main.java:262)
	at net.minecraftforge.launcher.Main.main(Main.java:57)
Caused by: java.lang.module.ResolutionException: Modules mixinextras.common and MixinExtras export package com.llamalad7.mixinextras.lib.semver.util to module net.minecraftforge.forge
Dominant language
Java
Stars
574
Forks
450
Avg merge
16h 20m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MinecraftForge/ForgeGradle

All issues in MinecraftForge/ForgeGradle

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.