gluegen.git - GLUEGEN repository on http://jogamp.org/ ;

	Commit message (Collapse)	Author	Age	Files	Lines
*	Bug 1417 - Android: Manifest-android can no more have 'Name: <folder>' ↵	Sven Gothel	2019-12-10	1	-6/+0
\| \| \| \| \| \| \| \| \|	directives for apk The 'Name <folder>' leads new apk to claim the missing resources (the folder actually) and fails to install the apk. Hence removed tagging the folders sealed.
*	Bug 1369: SCC: Hide SHA Algorithm bit size in literals of Specification	Sven Gothel	2019-04-03	1	-5/+5
\| \| \| \| \|	Implementation currently uses 256 bit Secure Hash (SHA) algorithm, but this may change in the future. Hence only use 'SHA' in the names, not 'SHA256'.
*	Bug 1369: Source Certification Contract (SCC): Initial SHA256 fingerprint & ↵	Sven Gothel	2019-04-03	1	-0/+5
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	runtime validation This change implements a strong SHA256 signature over: 1) source tree inclusive make recipe (SHA256-Source) 2) all class files (SHA256-Classes) 3) all native libraries (SHA256-Natives) 4) the class files as deployed in the jar (SHA256-Classes-this) 5) the native libraries as deployed in the jar (SHA256-Natives-this) and drops all of these in the deployed Jar file. This allows SHA256 validation of (4) + (5) at runtime and further complete validation (1), (2) and (3) offline. Full SCC would now required (1) - (3) to be placed on a server for further validation. Optionally we may use GPG <https://gnupg.org/> or PGP to validate the build entity to implement the chain of trust <https://en.wikipedia.org/wiki/Chain_of_trust> The SHA256 runtime validation is tested via: com.jogamp.common.util.TestVersionInfo
*	Jar Manifest: Seal all packages ; Each jar is 'standalone' as required by ↵	Sven Gothel	2014-01-25	1	-0/+3
\| \| \| \|	'sealed packages': gluegen-rt.jar < gluegen-rt-android.jar < gluegen.jar
*	Jar Manifest: Sealed Entries must follow generic headers - Otherwise ↵	Sven Gothel	2014-01-25	1	-2/+3
\| \| \| \|	subsequent entries are not recognized
*	Jar Manifest: Add empty line before EOF (otherwise last line is cut-off - ↵	Sven Gothel	2014-01-22	1	-0/+2
\| \| \| \|	duh), add 'Application-Library-Allowable-Codebase: *'
*	Bug 881 - Add 'Application-Name' in Jar's manifest to avoid Java6 NPEs ..	Sven Gothel	2013-11-01	1	-0/+1
\|
*	Bug 758: Fix scripts and ant build files to work w/ Java7 (default now) ↵	Sven Gothel	2013-06-20	1	-0/+4
\| \| \| \|	producing Java6 bytecode ; Apply JAR Manifest tags: Sealed, Permissions and Codebase
*	Bug 588: Adding jogamp.version property, i.e. 2.0.2-rc-<TIMESTAMP> used for ↵	Sven Gothel	2013-03-28	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \|	Manifest ; Common jogamp_int_version for Android. Until 2.0.2 gets released, the version string is 2.0.2-rc-<TIMESTAMP> and used in the Manifest for IMPLEMENTATION_VERSION. The previous build version name of IMPLEMENTATION_VERSION goes into the new tag IMPLEMENTATION_BUILD. Further more, we use a common jogamp_int_version for Android, to make life more easy.
*	Fix Bug 583 (2): Remove Android compile-time dependencies and exclude ↵	Sven Gothel	2012-06-15	1	-0/+13
	Android specific classes for non Android platforms Ensure same Java JAR content regardless of build target (fix). Separate Android compilation results to gluegen-rt-android.jar, avoiding generating different content of gluegen-rt.jar w/ non android builds. aapt.signed: @{android.abi} argument is 'generic' by default. Adding ${android.abi} to APK target name (gluegen-rt-android-armeabi-v7a.apk) if not generic.