Bug 398

Summary: Provide OSGi Metadata In Builds
Product: [JogAmp] Jogl Reporter: Ed Kohlwey <ekohlwey>
Component: coreAssignee: Sven Gothel <sgothel>
Status: CONFIRMED ---    
Severity: enhancement CC: ghislain_nadeau, sgothel, wwalker3
Priority: P5    
Version: 2   
Hardware: All   
OS: all   
Type: --- SCM Refs:
Workaround: ---

Description Ed Kohlwey 2010-05-18 05:55:15 CEST
An increasingly large number of organizations are using JOGL in OSGi, each one individually adding their own MANIFEST.MF. It would be nice to see a standard manifest packaged in the JOGL jars.
Comment 1 Wade Walker 2011-07-23 02:29:19 CEST
Recent discussion of this at http://forum.jogamp.org/UnsatisfiedLinkError-when-trying-to-use-JOGL-in-an-Eclipse-plugin-td3178913.html#a3189906. More specifically:

On Wednesday, July 20, 2011 09:44:05 PM Wade Walker [via jogamp] wrote: 
> 
> I can try it, but you'll have to tell me where our packaging script is and 
> how to test it (so I can make sure I don't mess it up). 

repo: jogamp-scripting 

https://jogamp.org/chuck/view/fwd/job/jogamp-scripting-promote-last-builds-master/

The above is the manual kicked off aggregation script: 

+++
#!/bin/bash 
mkdir -p log 
./hudson-builds/promote-latest-builds.sh master secure 2>&1 | tee log/jogamp-scripting-promote-last-builds-master-$(date +%Y%m%d%H%M).log
+++

If this helps as an entry to generate such OSGI bundle, awesome. 
Ping me (here, email, chat, ..) if I can help. 

ofc .. we still have to try to re-org the final release URLs and bundling, 
i.e. Rami, John and I thought it will be nice to have one zip for devs containing all components, gluegen, .. with the binaries and javadoc. 

we also like to have fixed URLs for each (old) version, just in case a user likes to link to a specific one. 

Cheers, Sven
Comment 2 JSlain 2013-07-16 04:35:55 CEST
Actually, this would still be usefull...