| Fat Jar Export: Could not find class-path entry [message #1863999] |
Sun, 10 March 2024 17:07  |
 Tapio Palomäki
Messages: 20
Registered: November 2023 |
Junior Member |
|
|
I have set up three user libraries to contain generic lwjgl libraries, windows libraries and linux libraries.
When a run time configuration is set to have generic + windows, the export of runnable java works.
when a run time configuration is set to have generic + linux, the export fails. all paths and configurations should be correct. whats wront?
This should be as simple as having two separate configurations for two different export runnable builds. nothing else is different than the windows to linux library change. should not fail but still it fails.
Yes I copied the original working run configuration for windows and renamed and changed the native user library from windows to linux.
It's even more confusing when you think working windows run config has items in modulepath and it still works. And I'm running on windows so no actual running the linux on this, just building the export runnable jar.
Edit: does not work even if moving the launch configuration modulepath libraries to classpath. Run configurations should be 100% separate from build configurations, but this might not be the case, as I dont have the linux natives in the build configurations modulepath or classpath.
Solution: build configuration modulepath and classpath affect run configurations. and it should not.
Error:
Jar export finished with problems. See details for additional information.
Fat Jar Export: Could not find class-path entry for 'C:eclipse/pkg/lwjgl3-3.3.3-bin/lwjgl/lwjgl-natives-linux.jar'
Fat Jar Export: Could not find class-path entry for 'C:eclipse/pkg/lwjgl3-3.3.3-bin/lwjgl-glfw/lwjgl-glfw-natives-linux.jar'
Fat Jar Export: Could not find class-path entry for 'C:eclipse/pkg/lwjgl3-3.3.3-bin/lwjgl-opengl/lwjgl-opengl-natives-linux.jar'
[Updated on: Sun, 10 March 2024 17:23] Report message to a moderator |
|
|
| Re: Fat Jar Export: Could not find class-path entry [message #1864493 is a reply to message #1863999] |
Tue, 19 March 2024 21:43  |
Joe Abraham
Messages: 2
Registered: March 2024 |
Junior Member |
|
|
I'm encountering the exact same issue. It's puzzling because setting up separate configurations for different export runnable builds seems straightforward, yet I'm facing problems specifically when configuring for generic + Linux.
I also copied my original working run configuration for Windows, made the necessary adjustments for Linux, ensuring all paths and configurations are correct. However, despite these efforts, the export still fails with the same error messages you've mentioned. What's particularly baffling is that the Windows run configuration works smoothly even with items in the modulepath, while the Linux one doesn't, despite mirroring the setup closely.
I've tried various adjustments, including moving the launch configuration modulepath libraries to the classpath, but to no avail. It's disconcerting to realize that the build configuration's modulepath and classpath seem to affect run configurations, which ideally shouldn't be the case. The error messages specifically point to the absence of class-path entries for the Linux natives, even though they are correctly configured in the run configuration. This discrepancy between configurations is perplexing. If anyone has encountered a similar issue or has insights into how to resolve this, I would greatly appreciate the assistance. Thank you in advance for any help provided.
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02518 seconds
] 
Search
Help
Register
Login
Home
