One example of what will happen is that the list of classes and packages that appears in the "Classes with Tracing disabled" list will be filtered by the lower SKU and saved, so when you run the higher SKU, you will only see those classes that are available in the lower SKU.

Another problem can occur if you later uninstall one of the two SKUs. JBuilder creates a default JDK definition in the JBuilder Home directory that points to the JDK distributed with JBuilder. When two SKUs of the same version of JBuilder are installed, the second SKU installed will not create this JDK definition because a JDK definition has already been created by the first version, pointing to the JDK in the install directory for the first JBuilder version. If you later uninstall the first version, the JDK definition remains, so the JDK definition used by the second JB version points to the JDK from the first version, which is no longer there. As a result, nothing will compile or run.

The solution to this is pretty simple. Simply edit the "jbuilder.config" file, located in the JBuilder /bin directory, and specify a different JBuilder Home directory. For example, I add the following to the config file for every Foundation version I install:

   # Alternate home directory for Foundation versions
   vmparam -Djbuilder.home=C:/jpm/.jbuilderF

The result is that the home directory for JBuilder 2005 foundation on my system is C:/jpm/.jbuilderF/.jbuilder2005, so I have no conflicts.
2006-Feb-05 7:12pm dave@davenet.net, gyles19@visi.com