I fixed the Pas Suite modules Tony listed. One impediment was what appears to be a new bug in Maven with paths containing spaces. To work around it, I renamed "Pas Suite" to "pas-suite" and "Pas Learner Runtime" to pas-learner-runtime in my checkout. I also had to fix the pom.xml for pas-curnitmap. It specified its site URL instead of inheriting from pas-suite.
I made the site for sail-otrunk, but it's on tels.sourceforge.net because that project is in the TELS repo right now. I couldn't find sail-qtibindings in the TELS or SAIL svn repos. I checked in the edits for everything except renaming "Pas Suite" and "Pas Learner Runtime" since those edits would break Eclipse checkouts. We should consider normalizing those names though. -t On Apr 28, 9:28 pm, Anthony Perritano <[EMAIL PROTECTED]> wrote: > Thanks for your help Turadg. Heres some of the things i noticed: > > tels sourceforge site: > > Under Modules: > > 1.Pas Learner Runtime link comes up > blank.http://tels.sourceforge.net/pas-suite/pas-learner-runtime/index.html > > 2. Modules not present: > pas mozswing > pas curnitmap > > JavaDocs out of date: > pas-otrunk step > > on the sail sourceforge site > > 1. Modules not present: > sail-otrunk > sail-qtibindings > > -Tony > > On Apr 28, 2008, at 6:13 PM, Turadg wrote: > > > > > Done. Please check whether it turned out how you were expecting. > > > On Apr 28, 7:37 pm, "Hiroki Terashima" <[EMAIL PROTECTED]> wrote: > >> Hi Turadg, > > >> Can you update the javadoc on the sail sourceforge site by > >> Thursday? > > >> Thanks, > >> Hiroki > > >> On Sun, Oct 7, 2007 at 3:19 PM, Turadg Aleahmad <[EMAIL PROTECTED]> > >> wrote: > >>> I'm replying to SAIL-Dev so this can be in the searchable archive. > > >>> First, to log in to tels-develop from my home machine I had to > >>> update the > >>> IP whitelist. For some reason iptables-restore no longer handles > >>> spaces so > >>> I had to remove those. I also removed Ed's IPs. > >>>http://www.telscenter.org/confluence/display/TSB/Security > > >>> Then I checked out the project membership permissions. Everyone > >>> on the > >>> project has Shell Access, which is I think sufficient for updating > >>> the site. > >>> While I was in there, I removed Ed from the project members. > > >>> The web site is built by Maven so to update it you run Maven > >>> commands. > >>> Since they're not interactive, you need to have private-key > >>> authentication > >>> set up to shell.sourceforge.net . I have this set up and I think > >>> it makes > >>> sense to have just one person updating the web site. Since I've > >>> been doing > >>> this, I propose that I stay in this role. > > >>> For reference though, here's how I do it: > >>> ssh tels-develop > >>> cd ~/sail > >>> svn up > >>> cd ~/sail/trunk > >>> mvn clean site > >>> mvn site-deploy > > >>> Sometimes it works that easily. Sometimes it takes some > >>> debugging. I've > >>> done it with the latest code and you can see the AUDIT07 marker up > >>> there. > >>> Incidentally, maybe the AUDIT07 should go on a different line > >>> because right > >>> now it's showing up as part of the class author. > > >>>http://sail.sourceforge.net/sail-core/apidocs/net/sf/sail/core/entity > >>> ... > > >>> -t > > >>> On 10/5/07, Hiroki Terashima <[EMAIL PROTECTED]> wrote: > > >>>> Turadg, > > >>>> What is needed to update the javadoc here: > >>>>http://sail.sourceforge.net/sail-core/apidocs/index.html > > >>>> Thanks, > >>>> Hiroki --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
