Ok so if I remember correctly. - you added a new dependency to the authoring tool pom (java help) - you wanted to make sure that dependency was correctly handled before checking in your changes which depended on that dependency.
So I interpreted "handling the new dependency" to mean two things: - the code you were about to check in would build successfully on continuum - the code you were about to check in would be available in the authoring tool jnlp, and it would not break the jnlp deployment process. You can verify that continuum has successfully picked up your new dependency by looking at it: http://www.telscenter.org/continuum/servlet/continuum/target/View.vm/fid/maven2Project/id/3 You can see in the dep list that javahelp is there. You can verify that the jnlp system is correctly using your new dependency by exampling the jnlp file the the authoring tool: Save this link to the disk and open it in a text editor: http://tels-develop.soe.berkeley.edu:8080/jnlp/org/telscenter/jnlp/authoring-everything-snapshot/authoring-everything-snapshot.jnlp Look for a reference to java help in it. If you rename it .xml and open with firefox it will be easier to read. So this should verify that your new dep is correctly picked up. At this point I don't see why you can't check in your code. The changes to the jnlp stuff I was making were to make the step of deploying jnlps easier. Instead of logging in and running a deploy step you can just click on the build link in confluence. This was related to your original issue, because some one needed to deploy the jnlps to verify that they have correctly picked up your new dependency. Scott On Thu, 2007-03-29 at 05:32 -0700, laurel wrote: > 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 -~----------~----~----~----~------~----~------~--~---
