Yes - of course I filed this as a bug. I can't justify $200 as a support incident though - particularly as this is clearly a bug in a preview release that just needs fixing.
Anyway, in the meantime I have found a workaround that works. You need to basically changing the symbolic link that references the current Java VM to point back to the older 1.4.2 distribution. This, of course, doesn't prevent you telling JBuilder to compile using the new 1.5.0, but makes JBuilder (adn all Java apps) run on the 1.4.2 VM by default. This is what modifying the Info.plist file should have done, but apparently doesn't.
Specifically, you need to:
- Open a terminal, then enter the following command line instructions:
- cd /System/Library/Frameworks/JavaVM.framework/Versions
- sudo unlink CurrentJDK
- sudo ln -s 1.4.2 CurrentJDK
sudo will ask you for an admin password. You may need to enable root account from within NetInfo Manager in order to do this - I'm not sure, as root is already enabled on my machine.
Paul
On Wednesday, January 11, 2006, at 09:25PM, Shawn Erickson <email@hidden> wrote:
>On 1/11/06, Paul Howland <email@hidden> wrote:
>> I hope Apple are looking into this
>
>Did you file a defect about it?
><http://developer.apple.com/bugreporter/>
>
>Did you consider opening a technical support incident?
><http://developer.apple.com/products/techsupport/tsget.html>
>
>> my Java development has now ground to a halt
>
>Developer previews are not meant to be used on systems that you must
>use (aka critical systems).
>
>-Shawn
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
