On Nov 17, 2010, at 1:23 AM, Jakub Skoczen wrote:
> On Tue, Nov 16, 2010 at 5:41 PM, Mike Swingler <email@hidden> wrote:
>> Yes, /usr/libexec/java_home should give the path to any system JDK or developer JDK installed in either the /System/Library, /Library, or ~/Library (Java/JavaVirtualMachines) locations.
>> It should not be necessary to create a symlink, just move the JVM you want to be your $JAVA_HOME up to the top in Java Preferences, and set $JAVA_HOME in your .bashrc, or other shell config you use. By default, if you use the Java command line tools that are already on your path from /usr/bin, they will just redirect to the right place automatically.
>> I'm curious, Jakub, what are you using the full path to the JDK for?
> To point NetBeans to the JDK -- it assumes certain location of the API
> docs and sources within that path. If it's not there you won't get any
> contextual help and "step into" core classes functionality. There's no
> way to point it to the exact location of the src/docs.jar (e.g to keep
> on using system JDK and have the docs elsewhere), it simply won't let
> you navigate within the JDK path. I could maybe overcome this by
> copying the jars out to some other location but instead I edited the
> netbeans.conf to say:
> 1.6.0.jdk is my symlink to the exact JDK build installed by the
> Developer Package.
I see. Well, the core issue is that NetBeans (like Eclipse and InteliJ) will have to rev, and either support navigating into a bundle, or just allowing you to choose a top-level .jdk bundle, and inferring the Contents/Home path inside it. Eclipse is going so far as to parse the output from "/usr/libexec/java_home --xml", and present a nice list of installed JVMs.
Until NetBeans revs, the temporary symlink seems like a reasonable workaround.
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden