Thinking about this situation, I want to clarify one point. When upgrading my JessDE (i.e. from a4 to a5), I reuse my existing workspace. In other words, I do the following:
O Shut down Eclipse. O Delete the gov.sandia.... Directories from the plugins directory. O Unzip all four .zip files from the Jess 'eclipse' directory into my Eclipse directory. O Start Eclipse. I'd just like to confirm that its safe to reuse your workspace across JessDE versions. -Mitch -----Original Message----- From: Mitch Christensen [mailto:[EMAIL PROTECTED] Sent: Sunday, February 13, 2005 7:33 AM To: [EMAIL PROTECTED]; 'Jess Mailing List' Subject: RE: Significant strangeness in JessDE 7.0a5 Oops. Sorry for not noticing this sooner, but my workspace .log is loaded with exception stacktraces. I've attached a small sampling of my .log file (this actual .log is 3.4Meg. FWIW, I just restarted Eclipse and the edits I made yesterday are gone yet again (3rd time now). There has to be a cached copy of that file somewhere in the workspace. I'm going to try with a fresh workspace. -Mitch -----Original Message----- From: Mitch Christensen [mailto:[EMAIL PROTECTED] Sent: Sunday, February 13, 2005 7:16 AM To: Jess Mailing List Cc: mtc Subject: Significant strangeness in JessDE 7.0a5 Hey, I've been doing some serious development over the weekend using 7.0a5 and have noticed (and verified) some rather strange behavior. First off, I should state that I'm simply living with the (apparent) memory leak for now since I haven't had time to do the profiling that was suggested (yet). I restart Eclipse every couple of hours when the 'save' times start getting unbearably long. More serious than this is is the fact that saves to disk don't always seem to happen, or perhaps older data seems to get written to disk. Here is what is happening. I am doing development/debugging using both the Java and Debug perspectives, switching frequently back and forth between the two. I step through my program for a while until I discover a bug, then I fix the bug (in either perspective), save, re-test and continue. At one point I found a rather significant logic error that required changes in several places in my code (in one file). I made the changes, re-tested and confirmed that the fix worked. Shortly thereafter I noticed 'save' slowness so I restarted Eclipse. My first test following the restart showed the same symptoms that I had previously fixed. Looking at the code I noticed that all the edits I had made to fix my logic error were gone. I have reproduced the symptom again this morning with different edits. I have never noticed this before I started editing code within the Debug perspective. Unfortunately I've got some heavy deadlines so I can't take time to analyze this right now, but I wanted to report it in case anyone else experience similar symptoms, or had time to look into it. My system config: OS: Windows XP Pro, 5.1.2600 Service Pack 2 Build 2600 Eclipse: 3.0.1 C:\>java -version java version "1.4.2_05" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04) Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode) -Mitch -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
