search

CrackedPolishedBlackstoneBricksMC / voldeloom

Voldeloom But Weird
MIT License
18 stars 2 forks source link

New 1.4.7 project - "Could not resolve org.lwjgl.lwjgl:lwjgl:2.9.1-nightly-20130708-debug3" #4

Open unilock opened 1 year ago

unilock commented 1 year ago

Hi! I'm trying to create a mod for 1.4.7 based off the template in sample/1.4.7. However, when I attempt to import the project into IntelliJ, I get the error: "Could not resolve org.lwjgl.lwjgl:lwjgl:2.9.1-nightly-20130708-debug3"

The same error can be seen when running ./gradlew runClient --info --stacktrace manually; here's the output of that: https://gist.github.com/unilock/c3c2705ff9f5fd607a58cffeb3812c41

The POM it mentions (at libraries.minecraft.net) appears to have ${project.groupId} as its groupId and ${project.version} as its version; is that intentional?

EDIT: I am using macOS 13.4.2 (aarch64).

unilock commented 1 year ago

This appears to be an issue only on aarch64. Using Adoptium's x86 build of Java 8 makes no difference, but using an x86-based Linux system works fine. See below!!

unascribed commented 1 year ago

Specifically 1.4.7 contains a weird alternate LWJGL2 dependency for macOS 10.5: image

The 2.9.1 debug build it pulls in has broken POMs because building LWJGL2 is a nightmare and 2013 Mojang didn't do it correctly.

Why this is being triggered on modern aarch64 macOS I have no idea. I suspect this has to do with macOS in general, not specifically aarch64. It's because VersionManifest does not check version constraints.

I question if Voldeloom should even be listening to these dependency declarations — for example, Prism completely ignores them and always subs in the latest 2.9.4 LWJGL2 nightly.

unilock commented 1 year ago

I made a fork that "fixes" this by checking the "os.version" field in dependency version manifests: https://github.com/unilock/voldeloom/commit/e184d625863702ef202412f2df32b3a92c706a8f

I'm not sure if this is the desired solution, though, hence no pull request.

BLOKBUSTR commented 8 months ago

I'm experiencing this same exact problem on the 1.6.4 sample in IntelliJ on MacOS 11.4 (aarch64). Alongside this, I'm receiving other errors like this:

Screen Shot 2023-10-23 at 9 50 19 PM

Seeing the above linked commits though, is this issue still considered "open"? What's the status on it?

quat1024 commented 8 months ago

I'm aware this is still an issue, i just haven't had time to work on voldeloom in a while