Hi Scott, I understand from yesterday's meeting that the above email was supposed to alert me to the fact that I could check in my additions to the authoring tool, possibly without causing problems by the added dependencies on the javahelp jars.
Below I have cut and pasted your instructions for what I originally needed to do (once you had fixed the deploy script) * run the deploy.sh script on tels-develop. (note: this script is currently broken because of memory issues, scott will send a note to sail-dev when it is fixed again.) Unfortunately, am finding your email above very much a mystery as I don't know how the changes to the jnlp's relate to my task. Can I just check in my code or do I need to do something first?? Do you have time to chat live with me about this today (skype - I'm free until 12 EST - then meeting with Hiroki) or else to explain things in an email. Whichever works best for you. Laurel On Mar 22, 7:53 am, Scott Cytacki <[EMAIL PROTECTED]> wrote: > I've finally got the new jnlp stuff setup. > > There is a new location to get the > jnlps:http://tels-develop.soe.berkeley.edu:8080/jnlp/ > > The directory layout now more closely matches the standard maven layout. > This includes the jnlp files themselves. So the place to find a jnlp > file is > here:http://tels-develop.soe.berkeley.edu:8080/jnlp/org/telscenter/jnlp/ > > Now every jnlp is timestamped. Previously only the > plr-everything-jdic-snapshot was timestamped. > > So if you want a jnlp that should work forever, because it never > changes, refer to one with a timestamp on the end. > > You can updated the jar files and jnlp files in this servlet context > with a continuum build now. Just go to the telscenter > continuum:http://www.telscenter.org/continuum/servlet/continuum/ > and build the project "Pas JNLP Parent". You do not need to login to do > this. It should only take about a minute to run. > > And now because we are not redeploying the servlet for each update, we > can use the jnlps in this servlet context "/jnlp" for production runs. > Previously we were redeploying the "/maven-jnlp-snapshot" context each > time there was an updated jar. This redeploying took a while, during > which time the files in that context were not available. So that is why > we had a separate context "/tels-jnlp" for production runs. We only > deployed "/tels-jnlp" during non school hours. > > That is the past now we only have to worry about one context "/jnlp". > > Scott --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
