To avoid problems from caching, on windows, here is what I do, I think this is sufficient:
1) kill the tomcat process; this is important, on windows it tends to hold onto open files. 2) svn update to the revision you want 3) do "ant clean build" 4) restart tomcat 5) may need to do an "ant webapp.deploy" if you did a "ant webapp.undeploy " earlier 6) In your browser clear all caches; in Firefox I click on Tools->Clear Private Data, and check the "Cache" checkbox 7) reload your test app into the browser On 9/24/07, Donald Anderson <[EMAIL PROTECTED]> wrote: > I finally got a Windows environment going, and can see the problem. > I have confirmed it shows up in #6548 and that it does not in #6547. > I built in two different fresh directories to avoid any cache problems. > For me it is Windows only, doesn't show if the server is OSX. > > Back in my (broken) trunk on Windows, I replaced the source files > that I had changed with > the old (6547) versions, and I still see the problem (after a clean > build). I guess I have > to create a new trunk directory for each test to reliably avoid cache > issues...? > This may be some hard slogging today to get this. > > - Don > > On Sep 24, 2007, at 9:42 AM, André Bargull wrote: > > > I got that error when I compiled the first time to the new trunk. > > So I don't see how Windows could be involved into this issue. > > In addition to that, trunk works for me in rev. #6539, therefore > > this is most likely linked to rev. #6548. > > > > This is my current trunk history: > > > > 1. #6548 or #6550 => first time I've checked out, must have been > > either 6548 or 6550; trunk was erroneous for me > > 2. #6529 => switched to first changeset of Don, recompiled > > everything => no errors > > 3. #6548 => switched to the second changeset of Don, recompiled > > everything => got theses errors > > 4. #6539 => switched back to the previous revision => no errors > > > > I can switch to #6548 or later, compile a simple application, and > > send it to you. So we can check if this is related to Windows, > > FlashPlayer or whatever... > > > > > > André > > > > P T Withington wrote: > >> Is it possible that this is related to Windows' penchant for > >> hanging on to old files? Did you stop/start your tomcat, clear > >> your caches and all that mumbo when you updated? I don't see the > >> error either.... > >> > >> On 2007-09-23, at 13:01 EDT, Philip Romanik wrote: > >> > >>> Hi Don, > >>> > >>> I just tried this on XP (FF1.5 browser) and I see the same > >>> behavior that Andre reported. > >>> > >>> Phil > >>> > >>> > >>>> Hi Andre, > >>>> > >>>> I'm running on Mac OSX, and I've tried Safari and Firefox and > >>>> they work for me. > >>>> That is, I get a full debugger window, and can type in > >>>> Debug.versionInfo() and get results. > >>>> (I'm new to the laszlo environment, so that's about all I know > >>>> how to do in the framework). > >>>> I ran an IE6 browser on WinXP against my server (still on Mac) > >>>> and still no problem. > >>>> Attached is a screen shot of that, in case I'm not doing > >>>> something obvious to you. > >>>> > >>>> This is troubling, I'd expect a compiler issue would give a more > >>>> consistent disaster. > >>>> > >>>> Phil -- you run on WinXP, can you try a fresh trunk and see if > >>>> you get the same problem that Andre has? Thanks. > >>>> > >>>> - Don > >>> > >> > > > -- > > Don Anderson > Java/C/C++, Berkeley DB, systems consultant > > Voice: 617-547-7881 > Email: [EMAIL PROTECTED] > WWW: http://www.ddanderson.com > > > -- Henry Minsky Software Architect [EMAIL PROTECTED]
