-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: distinguish Maven artifacts using classifier, not artifactId #3
Comments
Hi, One reason for me to avoid doing this would be to keep JOGL working as it has been for years... lot of JOGL users are used to version 2.3.2 / published in 2015... |
Without the fix above: JOGL throws an The reason nobody noticed is because The repro is simple… Run a simple program like this (enough to ensure that import com.jogamp.opengl.GLProfile;
public class Main {
public static void main(String[] args) {
System.out.println(GLProfile.isInitialized());
}
} It goes bang: Because it tries to invoke
TempJarCache.initSingleton();
JNILibLoaderBase.addNativeJarLibs(new Class<?>[] { jogamp.common.Debug.class }, null);
The convention for how to invoke
Now, maybe:
But this
Is that satisfiable? From what I can tell (looking at Cubism Editor), the convention for loading native libs on Nevertheless, I think you do have the option of publishing the artifact to both coordinates. |
Thank you @Birch-san for the detailed explanations.
Since 2.3.2 (and even earlier), I have been used to only work with the jar files, letting JOGL deal with unpacking the native libraries to a tmp dir (which by the way fails on Ubuntu 18). I tried reproducing the link error on my Mac M1 by adding the VM arg
Why do you think we have difference between our two run? |
It's helpful for
gluegen-rt-v2.4.0-rc4.jar
andgluegen-rt-v2.4.0-rc4-natives-macosx-universal.jar
to be installed to the same directory:This enables compatibility with calls such as:
addNativeJarLibs
locatesgluegen-rt-v2.4.0-rc4.jar
correctly, and assumes thatgluegen-rt-v2.4.0-rc4-natives-macosx-universal.jar
will be located next to it.You can achieve this by making the two artifacts agree on artifactId, but differ by classifier:
The text was updated successfully, but these errors were encountered: