Answers in this category:
Code Insight doesn't work inside JSP files.
Compiling code containing JDK 1.4's new "assert" keyword while an earlier JDK (1.3.1 or earlier) is selected causes an Error #: 2301: internal compiler error: java.lang.NullPointerException.
In Project Properties | Run | Test tab, only two JUnit Test Runners are available, the JUnit Text UI, and the JUnit Swing UI. The JBTestRunner selection is not present. Sometimes, though, it appears, but often it doesn't.
I have a project that contains an EAR, and every time I build it, my modem dials up my ISP. What's going on?
Error #: 2301 : internal compiler error: java.lang.ArrayIndexOutOfBoundsException
JBuilder 6 Compile Errors - a Workaround
Infinite compiles
Methods on Object lost through Interfaces

I don't have a 1.4 beta on my home machine to test this with fully, but I can still reproduce the NPE:

Create a one-class project and assign it a 1.3.1 JDK.

Selecting different target JDKs (IE 'all', 'JDK 1.2', 'JDK 1.3', or 'JDK 1.4') doesn't matter, the error still appears.

Leave asserts disabled (Project Properties | General), project compiles but you get a 'no such method' error on the assert line.

Enable asserts. Now you get a 2301 error and the following appears in the -verbose output:

  java.lang.NullPointerException
        at com.borland.compiler.frontend.Unop.b(Unknown Source)
        at com.borland.compiler.frontend.Assignop.b(Unknown Source)
        at com.borland.compiler.frontend.AST.c(Unknown Source)
        at com.borland.compiler.frontend.Exec.b(Unknown Source)
        at com.borland.compiler.frontend.AST.c(Unknown Source)
        at com.borland.compiler.frontend.FunDef.a(Unknown Source)
        at com.borland.compiler.frontend.FunDef.b(Unknown Source)
        at com.borland.compiler.frontend.AST.c(Unknown Source)
        at com.borland.compiler.frontend.ClassDef.a(Unknown Source)
        at com.borland.compiler.frontend.TopLevel.a(Unknown Source)
        at com.borland.compiler.frontend.JavaCompiler.a(Unknown Source)
        at com.borland.compiler.frontend.JavaCompiler.compile(Unknown Source)
        at com.borland.compiler.frontend.JavaCompiler.compile(Unknown Source)
        at com.borland.javamaker.ProjectEntry.a(Unknown Source)
        at com.borland.javamaker.a.compile(Unknown Source)
        at com.borland.javamaker.x.make(Unknown Source)
        at com.borland.javamaker.x.a(Unknown Source)
        at com.borland.javamaker.ProjectEntry.compile(Unknown Source)
        at com.borland.javamaker.ProjectEntry.make(Unknown Source)
        at com.borland.javamaker.NewJavaMaker.makeThem(Unknown Source)
        at com.borland.jbuilder.build.JavaBuildTask.build(Unknown Source)
        at com.borland.primetime.build.BuildProcess.run(Unknown Source)
        at java.lang.Thread.run(Thread.java:484)

Workarounds:
If you must compile with a 1.3.1 or earlier JDK, you should disable the assert keyword (Project Properties | General) and then:

  1) comment out or delete all asserts already in the code;
  2) provide an assert method somewhere where each class can find it:
 

     public void assert( boolean exp ) {}

This will allow the project to compile and run until you have a 1.4-compatible JDK available.

2002-Jan-05 8:37am gyles19@visi.com

   java.lang.NullPointerException
        at com.borland.jbuilder.jot.src.eb.c(Unknown Source)
        at com.borland.jbuilder.jot.src.cc.h(Unknown Source)
        at com.borland.jbuilder.jot.src.eb.getDeclaredName(Unknown Source)
        at com.borland.jbuilder.jot.src.eb.getName(Unknown Source)
        at com.borland.jbuilder.jot.src.cd.execute(Unknown Source)
        at com.borland.jbuilder.jot.src.jd.seek(Unknown Source)
        at com.borland.jbuilder.jot.src.jd.hasNext(Unknown Source)
        at com.borland.jbuilder.jot.src.qc.a(Unknown Source)
        at com.borland.jbuilder.jot.src.nc.getDeclaredMethod(Unknown Source)
        at com.borland.jbuilder.jot.src.nc.getMethod(Unknown Source)
        at com.borland.jbuilder.cmt.jb.JbComponent.getMethod(Unknown Source)
        at com.borland.jbuilder.cmt.jb.JbComponent.h(Unknown Source)
        at com.borland.jbuilder.cmt.jb.JbComponent.q(Unknown Source)
        at com.borland.jbuilder.cmt.jb.JbComponent.init(Unknown Source)
        at com.borland.jbuilder.cmt.CmtComponentManager.getComponent(Unknown Source)
        at com.borland.jbuilder.cmt.CmtComponentManager.getComponent(Unknown Source)
        at com.borland.jbuilder.cmt.CmtComponentManager.getComponent(Unknown Source)
        at com.borland.jbuilder.designer.DesignerViewer.getComponentSource(Unknown Source)
        at com.borland.jbuilder.designer.inspector.InspectorView.a(Unknown Source)
        at com.borland.jbuilder.designer.inspector.InspectorView.setTarget(Unknown Source)
        at com.borland.jbuilder.designer.inspector.InspectorView.init(Unknown Source)
        at com.borland.jbuilder.designer.inspector.Inspector.a(Unknown Source)
        at com.borland.jbuilder.designer.inspector.Inspector.init(Unknown Source)
        at com.borland.jbuilder.designer.i.run(Unknown Source)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:154)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:337)
        at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:131)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:98)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:85)                                   

The JBuilder Test Runner OpenTool is assigned to the Wizards group (probably not the best choice.) So, if you haven't triggered anything that would cause the Wizards group to be initialized, the JBuilderTestRunner won't appear in the selection list under Project Properties | Run | Test.

A simple work around for this is to click on the Wizards menu item and wait a moment for the wizards menu to appear. Now the wizards are initialized, and JBuilder Test Runner should appear in the Project Properties | Run | Test tab.
2002-Jan-05 9:17am gyles19@visi.com

This remote access to Sun's website is what is causing your machine to dial out. To prevent this from happening, change the DOCTYPE to point to a local copy of the DTD.

Have you had projects that compiled without a problem in JBuilder 5, only to
have them fail to work in JBuilder 6?  Have you had problems with classing 
being built, only to have the JVM say that the classloader can't find the 
class?  Here's a workaround I developed that seems to have solved these  
problems for me.

First in your \jbuilder6\bin\jbuilder.config file add the following line:

vmparam -Duse.old.bmj

Next, start JBuilder 6.  Open your project.  From the main menu select Project
| Project Properties.  Choose the 'Build' tab.  Be sure two options are 
CHECKED:

- Check stable packages.
- Make stable packages.

Doing this seems to have fixed all build errors for me.

1) Project Properties | Build | Target VM -> All SDKs (For some people, setting this back wasn't enough, they had to manually edit the jpx file and delete the property completely.)

2) Project Properties | Build | Check Stable Packages and Make Stable Packages -> Enable

3) Edit jbuilder.config and add the following and restart JBuilder:

       vmparam -Duse.old.bmj

You may need to delete the classes/package cache stuff after making any of the above changes. You may also need to apply a combination of the above.

2002-Apr-03 9:00am gyles19@visi.com

 public class B implements XYZ{
  B(){
   test2(this);
  }
  public static void main(String [] vars){
   new B();
  }
  void test2(XYZ interf){
   Class c = interf.getClass(); //does not work
 //  Class c = ((Object)interf).getClass(); //does work
   System.out.println("class is " + c);
  }
 }
 interface XYZ{};

This does not happen from the command prompt. JBuilder is not kind enough to let us see its compile as it does its execution command either...
2002-Jun-07 3:37pm lamont_gilbert@rigidsoftware.com, gyles19@visi.com

The more common symptom of this problem is the infinite compile loop.
2002-Jun-08 8:42pm gyles19@visi.com