Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Running JBuilder after Java 1.4.1 breaks it Apps
I had a perfectly good version of JBuilder Personal 7 running before I did a system update and updated my JavaVM to 1.4.1 from 1.3.1, and JBuilder failed to work after that. Having a pretty important project due soon, I tried everything. Eventually I wiped out the entire drive and installed OS X from scratch.

At this point, I thought 1.4.1 wasn't the problem, but a clean install of JBuilder after the update still wouldn't work. Knowing that JBuilder is simply a HUGE Java app anyhow, I decided to run the class from the command prompt. Here's the long classpath that gets this behemoth up and running:
java -cp /System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Classes/classes.jar:
../patch:../lib:../lib/ext:../lib/TabbedPaneFix.jar:../lib/lawt.jar:../lib/jbuilder.jar:
../lib/gnuregexp.jar:../lib/help.jar:../doc/jb_ui.jar:../lib/activation.jar:../lib/ant.jar:
../lib/beandt.jar:../lib/dt.jar:../lib/dx.jar:../lib/jbcl.jar:../lib/optional.jar:
../lib/xerces.jar com.borland.jbuilder.JBuilder
**Note that everything above should be all on one line with no spaces between the class path items.

[robg adds: I don't have JBuilder, so I can't test this, and I hope I didn't mess up the command while formatting it for display. Please let me know if I did!]
    •    
  • Currently 2.75 / 5
  You rated: 2 / 5 (4 votes cast)
 
[5,405 views]  

Running JBuilder after Java 1.4.1 breaks it | 7 comments | Create New Account
Click here to return to the 'Running JBuilder after Java 1.4.1 breaks it' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Running JBuilder after Java 1.4.1 breaks it
Authored by: staze on Mar 13, '03 10:20:46AM
The Apple Dev site addresses this: link. JBuilder 7 now works as normal after applying this fix. You'll want to go to the Tools->Configure JDKs... menu to add 1.4 as a VM option. You can then change the VM for a project in the Path tab in your Project Properties.

[ Reply to This | # ]
Running JBuilder after Java 1.4.1 breaks it
Authored by: ravedog on Mar 13, '03 02:42:29PM
from the MacFixIt site:

Fix for JBuilder 7 We previously reported that ince Java 1.4.1 has been installed, JBuilder 7 stops working. Apple has now posted a developer note offering a solution:

  1. In your JBuilder7 folder, navigate to JBuilder.framework/bin/
  2. Open the jdk.config file in a text editor. You may need to do this from the shell with the sudo command depending on how the permissions to JBuilder7 are set. For example, type sudo vi jdk.config
  3. Add the following line: javapath /System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Libraries/libjvm_compat.dylib.
  4. Save the file and launch JBuilder7 by double clicking the icon.


[ Reply to This | # ]
Running JBuilder after Java 1.4.1 breaks it
Authored by: craig on Mar 13, '03 04:39:26PM

I tried that, but JBuilder is still using Java 1.3.1 (you can tell by choosing About JBuilder, then clicking on the Info tab). The only way to get it use 1.4.1 is from the command line.



[ Reply to This | # ]
Running JBuilder after Java 1.4.1 breaks it
Authored by: stevechamp on Mar 23, '03 03:50:40PM

This worked for me!

Thanks much,
Steve C.



[ Reply to This | # ]
Running JBuilder after Java 1.4.1 breaks it
Authored by: 3film on Mar 13, '03 09:16:55PM

I got ravedog's method to work after some time, the path doesn't include the fullstop at the end, so the path is:

javapath /System/Library/Frameworks/JavaVM.framework/Versions/1.4.1/Libraries/libjvm_compat.dylib



[ Reply to This | # ]
Running JBuilder after Java 1.4.1 breaks it
Authored by: RobFrenchick on Oct 30, '03 03:10:13PM

I used the fix that you prescribed and it worked great for 12 computers, but not for 2 others. Do you have any other suggestions?



[ Reply to This | # ]
Running JBuilder after Java 1.4.1 breaks it
Authored by: stcato on Mar 04, '04 10:37:29AM

Since installing Java 1.4.1 JBuilder 7 no longer works - but changing the 1.4.1 in the jdk.config file in text edit solves the problem (see 3film's note of Mar 13th 03)



[ Reply to This | # ]