JBuilder is a very good Java development tool for Borland, but it is high for machine configuration and is too low. The question to be solved this article is: By modifying the JBuilder profile, let it run on the 1.4 version of the Java virtual machine to improve the efficiency of the operation.
Platform: Windows 2000 Server Chinese version SP2
JBUILDER installation directory: D: / jbuilder7
JDK installation directory: c: /jdk1.4.1
JBuilder7 is running on JDK1.3.1 (D: /JBuilder7/JDK1.3.1), which can be viewed by clicking Help / About JBuilder / Info, mainly four items:
Java.vm.info | Mixed Mode
Java.vm.name | Java Hotspot (TM) Client VM
Java.vm.vendor | Sun Microsystems Inc.
Java.vm.Version | 1.3.1-b24
Open d: /jbuilder7/bin/jdk.config (recommended first backup), find the 14th line javapath ../jdk1.3.1/jre/bin/HOTSPOT / JVM.DLL modified to JavaPath C: /jdk1.4.1/jre/ BIN / Client / JVM.DLL, found 20 line addpath ../jdk1.3.1/lib/tools.jar modified to Addpath C: /jdk1.4.1/lib/tools.jar. Determine whether the deployment is not mistaken.
Restart JBUILDER, if you start a prompt error, make sure the path settings are correct. View the information again:
Java.vm.info | Mixed Mode
Java.vm.name | Java Hotspot (TM) Client VM
Java.vm.vendor | SUNMICROSTEM INC.
Java.vm.Version | 1.4.1-beta-b14
It can be seen that JBuilder has been running on JDK1.4. Now compile and run some previous Java projects, it can feel significantly improved speed.
Description: JDK1.4.1-beta-b14 used herein is still in the test stage, not very stable, no problem under the Windows interface, but when switching to Metal or CDE / Motif, other functions are normal.
