Workspace Errors : Cannot Resolve Import

[MineModder2000]

Just downloaded the recommended forge version for Minecraft 1.16.4 and followed all instructions. I ran gradlew genEclipseRuns then imported the project into Eclipse IDE but its giving me unresolved import errors for any non core java import. This means that

org.apache and all the net.minecraftforge imports are underlined in red with the message "the import cannot be resolved". Please help thanks.

 

 

[ChampionAsh5357]

Do not run the commands before entering eclipse. Get a clean MDK, open up a workspace, import as an existing gradle project, then once that's done run the command either through the IDE system (recommended) or in terminal.

[MineModder2000]

4 hours ago, ChampionAsh5357 said:

Do not run the commands before entering eclipse. Get a clean MDK, open up a workspace, import as an existing gradle project, then once that's done run the command either through the IDE system (recommended) or in terminal.

Thanks did the trick, it's been a while since I've done this stuff. Another issue now, it's says "Error: Could not find or load main class net.minecraftforge.userdev.LaunchTesting" when I hit run.

[ChampionAsh5357]

You could either try rerunning the generate runs again or target a different version of Forge temporarily, refresh, and then regen. One of those two tricks tends to annoy gradle enough to build them correctly.

[MineModder2000]

17 hours ago, ChampionAsh5357 said:

You could either try rerunning the generate runs again or target a different version of Forge temporarily, refresh, and then regen. One of those two tricks tends to annoy gradle enough to build them correctly.

Still no cigar. I dragged and dropped my old src files into the project folder, updated the toml file, rebuilt again but it still doesn't work.

[ChampionAsh5357]

Then try closing the IDE, running 'gradlew --stop' and then 'gradlew clean', opening up the IDE, refresh and regen. If that doesn't work, you can always repeat except deleting the .gradle folder first in your directory and then in your application data.

[MineModder2000]

1 hour ago, ChampionAsh5357 said:

Then try closing the IDE, running 'gradlew --stop' and then 'gradlew clean', opening up the IDE, refresh and regen. If that doesn't work, you can always repeat except deleting the .gradle folder first in your directory and then in your application data.

Sadly none of this worked either...

[ChampionAsh5357]

Try going into the run configurations then, locating 'runClient', and where it says Main class, click Search... and find the LauchTesting class applicable to yours. Maybe that will fix the issue.

[MineModder2000]

9 minutes ago, ChampionAsh5357 said:

Try going into the run configurations then, locating 'runClient', and where it says Main class, click Search... and find the LauchTesting class applicable to yours. Maybe that will fix the issue.

It doesn't find anything in the search, a clue that something is amiss.

[ChampionAsh5357]

Then you are definitely missing something within your imports. Did you delete both the .gradle folder within your workspace and the one located within user/.gradle? Remember that your workspace should be closed while this is happening. Hopefully this will remove any cache associated with Forge which might fix the issue.

 

If it still persists after all of this, then Gradle is just not on your side right now. Try again at a different time repeating the same steps maybe after a computer restart or two and it'll probably work because Gradle is like that sometimes.

[MineModder2000]

On 1/7/2021 at 7:35 PM, ChampionAsh5357 said:

Then you are definitely missing something within your imports. Did you delete both the .gradle folder within your workspace and the one located within user/.gradle? Remember that your workspace should be closed while this is happening. Hopefully this will remove any cache associated with Forge which might fix the issue.

 

If it still persists after all of this, then Gradle is just not on your side right now. Try again at a different time repeating the same steps maybe after a computer restart or two and it'll probably work because Gradle is like that sometimes.

I did in fact delete both, tried it again as well, and its been several reboots still nothing works. I have another gradle / libgdx project and it works fine...