🚀 go-pugleaf

I've just had a very frustrating experience trying to get JBuilder
(Student Professional version) to compile a project that I initially
wrote in JDK1.2(b2) on a Sun box.  
  I have installed the Swing 0.7 files on the system, and initially,
when I started building projects with Swing, it worked fine.  However,
now (the next day) building one always bombs with the error "Interfaces
cannot have inner classes", and showing a corrupted source file in the
browser.  
  The main project was a console-based parser.  Initially JBuilder
complained about redefined classes twice even though the files
containing the redefined classes were backups and were never imported or
included anywhere; JBuilder apparantly decided to compile them anyway. 
More problems resulted as the result of my using a package named CSP. 
This is fine, except that the filename is all caps and <8 characters
with the result that Win95 assumes it's a DOS filename and *sometimes*
refers to it as Csp.  JBuilder noticed the difference between CSP and
Csp, and complained that the "dependancies file was incorrect".  Well, I
didn't write the dependancy file, why didn't it rebuild it itself?   In
the end I had to scrub out the entire myclasses path in order to get it
to build.
  I would like to know if there's any way of doing the following:
- Abolish the dependancy file and have JBuilder compile only on the
  bases of what's imported.
- Automatically add to the project a single file and all its 
  dependancies.
- Open an inputtable console window in the debugger (my project, 
  currently console-based, couldn't be debugged because I couldn't
  find this.  When I tried typing in the DOS box the debugger appeared
  to be running it, JBuilder crashed and took Windows with it.)
- Get JBuilder to run a Save All whenever a compile takes place.
  (I wouldn't have lost work to the crash if it did this. :) )