Posted by Michael Bien on Feb 02, 2011; 4:30pm
URL: https://forum.jogamp.org/Re-incorrect-files-in-stable-release-tp2399074p2406549.html

  Hi Wade,

On 02/02/2011 04:28 AM, Wade Walker [via jogamp] wrote:
> Speaking of which, is it ever a good idea for JOGL web start users to point
> to http://jogamp.org/deployment/webstart/ in their JNLP files? It seems like
> this just creates the possibility of their app breaking whenever the newest
> JOGL changes something, with their local JARs staying the same.
good question :)

as Sven already mentioned: we have two webstart folders,
one for major releases and one for early access stuff (random builds).

Imagine it would be a maven repository. Its ok for testing when you
always take the latest version but for production you may have the
requirement to build from a internal maven repo against fixed/known
dependency versions (speak hosting the libs on your own server).

But you could still decide to link to our server (balls of steel as
precondition) which is absolutely fine since we can host every
incompatible version under a different namespace.

lets say JOGL 2 is released and we do a jogamp bundle.. we may host all
subsequent updates as
/webstart-2.0 as long we don't break compatibility.
If we break compatibility we just add another folder (e.g /webstart-2.5).

Developers could use the bleeding edge webstart-next for demos and
testing since they can live with the risk that it can break anytime.

The deployment isn't finished yet and we agreed to don't loose to much
time with it before 2.0... we can always optimize it later.

comments? :)

best regards,
michael

--
http://michael-bien.com/