Laurel,

The jnlp used for this offering:

   http://rails.dev.concord.org/sds/6/offering/6505

is called Otrunk Jnlp:

   http://rails.dev.concord.org/sds/6/jnlp/edit/4951

which points to a external jnlp resource at this location:

http://tels-develop.soe.berkeley.edu:8080/jnlp/org/telscenter/jnlp/plr-everything-jdic-otrunk-snapshot/plr-everything-jdic-otrunk-snapshot.jnlp

This is a snapshot jnlp and because always-update is (in the sds jnlp 
resources) is now set to true it means that source check-ins that 
compile correctly will generate new jars and a new jnlp.

I recommend creating at least two sds jnlp resources for using in a 
portal realm, one pointing to (and labeled descriptively) a snapshot 
release of the jars and one pointing to a frozen set of jars.

Take a look at this page in a browser to see all the various frozen 
jnlps for plr-everything-jdic-otrunk-snapshot.

http://tels-develop.soe.berkeley.edu:8080/jnlp/org/telscenter/jnlp/plr-everything-jdic-otrunk-snapshot/

So if your testing shows the current snapshot jnlp works this is what 
I suggest you do:

rename this sds jnlp resource

http://rails.dev.concord.org/sds/6/jnlp/edit/4951

to:

  OTrunk JNLP Snapshot

and create another sds jnlp resource

name: OTrunk JNLP Frozen
url: 
http://tels-develop.soe.berkeley.edu:8080/jnlp/org/telscenter/jnlp/plr-everything-jdic-otrunk-snapshot/plr-everything-jdic-otrunk-snapshot-0.1.0-20071212.080901.jnlp

it shouldn't matter what the always-update attribute is set to 
because this this jnlp and the jars it refers to sshould never change.

You can later change the url for the "OTrunk JNLP Frozen" sds jnlp if 
you determine a different frozen jnlp is more suitable.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"SAIL-Dev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/SAIL-Dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to