🚀 go-pugleaf

I found the solution.  
Don't use jbuilder at all.  Use eclipse, it's much better. Up and
running in 2 minutes, no problems at all - literally.
It's like dumping a noisy epson printer for an HP printer. You can't
compare the two. (although at least epson is good for high quality
color printing).
And it's not going anywhere, as it's endorsed by IBM,HP and others, is
open source, and has a large fan base.


marf@aceinternet.co.uk (David Taylor) wrote in message news:<aa120a36.0312251247.2350f710@posting.google.com>...
> I have a project consisting of 2 files.
> c:\j1.4\bin\plagCheck\StringInfo.java
> c:\j1.4\bin\plagCheck\StringManager.java
> 
> StringManager.java contains the main method.
> 
> When I compile them and run StringManager.class, I don't get any 
> Exceptions.  It completes.
> 
> However, if I try to debug it by
> I right click StringManager.java and click  "Debug using defaults"
> and step into the program.  
> As soon as it runs into 
> this line of code:
> stringsFound.add(new StringInfo(swPos, ewPos, str.substring(swPos,
> ewPos + 1)));
> It opens up a window displaying  java.lang.System  i'm forced to step
> into that.  This brings up sun.misc.Launcher which brings up
> java.lang.ClassNotFoundException which calls Exception. The list goes
> on.
> 
> I've browsed previous posts and verified the following
> 
> 1
> Tools...Configure JDKs - JDK Home Path=c:\j1.4  (this is correct
> so it can find c:\j1.4\bin\java.exe, and the rest)
> I temporarily tried referring to the c:\jb9\jdk1.4  but it didn't fix
> the problem.
> 2
> Project..Project Properties..Paths
> Every path(output,backup,working directory and source) are all 
> set to c:\j1.4\bin\plagCheck
> Project..Default project properties has the same settings.
> 
> 3
> Hovering the mouse over the files listed in the explorer pane,
> verifies that all files are located in c:\j1.4\bin\plagCheck
> 
> 4
> I reinstalled jbuilder in c:\jb9 because i thought maybe it'd work if
> the directory name is in 8.3 form.  Still didn't work.