Login  Register

Jar file name pedantry

Posted by tyro on Jun 22, 2012; 10:15pm
URL: https://forum.jogamp.org/Jar-file-name-pedantry-tp4025305.html

Hi. The current list of distribution jar names:

gluegen.jar
gluegen-rt-android-armeabi-v7a.apk
gluegen-rt-android-armeabi-v7a-unsigned.apk
gluegen-rt.jar
gluegen-rt-natives-android-armv7.jar
gluegen-rt-natives-linux-amd64.jar
gluegen-rt-natives-linux-armv7hf.jar
gluegen-rt-natives-linux-armv7.jar
gluegen-rt-natives-linux-i586.jar
gluegen-rt-natives-macosx-universal.jar
gluegen-rt-natives-solaris-amd64.jar
gluegen-rt-natives-solaris-i586.jar
gluegen-rt-natives-windows-amd64.jar
gluegen-rt-natives-windows-i586.jar
joal-armeabi-v7a.apk
joal-armeabi-v7a-unsigned.apk
joal.jar
joal-natives-android-armv7.jar
joal-natives-linux-amd64.jar
joal-natives-linux-armv7hf.jar
joal-natives-linux-armv7.jar
joal-natives-linux-i586.jar
joal-natives-macosx-universal.jar
joal-natives-solaris-amd64.jar
joal-natives-solaris-i586.jar
joal-natives-windows-amd64.jar
joal-natives-windows-i586.jar
joal-test.jar
jocl-armeabi-v7a.apk
jocl-armeabi-v7a-unsigned.apk
jocl.jar
jocl-natives-android-armv7.jar
jocl-natives-linux-amd64.jar
jocl-natives-linux-armv7hf.jar
jocl-natives-linux-armv7.jar
jocl-natives-linux-i586.jar
jocl-natives-macosx-universal.jar
jocl-natives-solaris-amd64.jar
jocl-natives-solaris-i586.jar
jocl-natives-windows-amd64.jar
jocl-natives-windows-i586.jar
jogamp.android-launcher.apk
jogamp.android-launcher-unsigned.apk
jogl.all-android-armeabi-v7a.apk
jogl.all-android-armeabi-v7a-unsigned.apk
jogl.all.jar
jogl.all-mobile.jar
jogl-all-natives-android-armv7.jar
jogl-all-natives-linux-amd64.jar
jogl-all-natives-linux-armv7hf.jar
jogl-all-natives-linux-armv7.jar
jogl-all-natives-linux-i586.jar
jogl-all-natives-macosx-universal.jar
jogl-all-natives-solaris-amd64.jar
jogl-all-natives-solaris-i586.jar
jogl-all-natives-windows-amd64.jar
jogl-all-natives-windows-i586.jar
jogl.all-noawt.jar
jogl.test-android.apk
jogl.test-android-unsigned.apk
jogl.test.jar

Would it be possible to fix the names of the jogl.* jar files for consistency with the others? This would make it much easier for us to automate processing of the jar files (right now, we special case jogl jars).

Any objections to changing things to:

gluegen.jar
gluegen-rt-android-armeabi-v7a.apk
gluegen-rt-android-armeabi-v7a-unsigned.apk
gluegen-rt.jar
gluegen-rt-natives-android-armv7.jar
gluegen-rt-natives-linux-amd64.jar
gluegen-rt-natives-linux-armv7hf.jar
gluegen-rt-natives-linux-armv7.jar
gluegen-rt-natives-linux-i586.jar
gluegen-rt-natives-macosx-universal.jar
gluegen-rt-natives-solaris-amd64.jar
gluegen-rt-natives-solaris-i586.jar
gluegen-rt-natives-windows-amd64.jar
gluegen-rt-natives-windows-i586.jar
joal-armeabi-v7a.apk
joal-armeabi-v7a-unsigned.apk
joal.jar
joal-natives-android-armv7.jar
joal-natives-linux-amd64.jar
joal-natives-linux-armv7hf.jar
joal-natives-linux-armv7.jar
joal-natives-linux-i586.jar
joal-natives-macosx-universal.jar
joal-natives-solaris-amd64.jar
joal-natives-solaris-i586.jar
joal-natives-windows-amd64.jar
joal-natives-windows-i586.jar
joal-test.jar
jocl-armeabi-v7a.apk
jocl-armeabi-v7a-unsigned.apk
jocl.jar
jocl-natives-android-armv7.jar
jocl-natives-linux-amd64.jar
jocl-natives-linux-armv7hf.jar
jocl-natives-linux-armv7.jar
jocl-natives-linux-i586.jar
jocl-natives-macosx-universal.jar
jocl-natives-solaris-amd64.jar
jocl-natives-solaris-i586.jar
jocl-natives-windows-amd64.jar
jocl-natives-windows-i586.jar
jogamp-android-launcher.apk
jogamp-android-launcher-unsigned.apk
jogl-all-android-armeabi-v7a.apk
jogl-all-android-armeabi-v7a-unsigned.apk
jogl-all.jar
jogl-all-mobile.jar
jogl-all-natives-android-armv7.jar
jogl-all-natives-linux-amd64.jar
jogl-all-natives-linux-armv7hf.jar
jogl-all-natives-linux-armv7.jar
jogl-all-natives-linux-i586.jar
jogl-all-natives-macosx-universal.jar
jogl-all-natives-solaris-amd64.jar
jogl-all-natives-solaris-i586.jar
jogl-all-natives-windows-amd64.jar
jogl-all-natives-windows-i586.jar
jogl-all-noawt.jar
jogl-test-android.apk
jogl-test-android-unsigned.apk
jogl-test.jar

If so, it would probably be best to do this now, before 2.0.