JDeveloper 12c on OS X

It's pretty cool that JDeveloper is now a NetBeans platform app.  Wanting to give it a quick look on OS X I downloaded the Java edition generic installation.

Unfortunately after unzipping it and placing it in Applications, it would not launch.

Trying from the command line using this command

open -n ./JDeveloper.app

gave me a error:

LSOpenURLsWithRole() failed with error -10810 for the file /Applications/jdeveloper/JDeveloper.app.

Given past history trying to get JDeveloper going on OS X I thought I might try the JAVA_HOME environment variable first.

First I checked which versions are available with this command:

/usr/libexec/java_home -V

this was the output:

Matching Java Virtual Machines (5):
    1.7.0_25, x86_64: "Java SE 7" /Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home
    1.7.0_21, x86_64: "Java SE 7" /Library/Java/JavaVirtualMachines/jdk1.7.0_21.jdk/Contents/Home
    1.7.0_17, x86_64: "Java SE 7" /Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home
    1.6.0_51-b11-456, x86_64: "Java SE 6" /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
    1.6.0_51-b11-456, i386: "Java SE 6" /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home


In order to set JAVA_HOME I ran this command:

export JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_25.jdk/Contents/Home

And finally from /Applications/jdeveloper I ran this:

open -n ./JDeveloper.app

HTH,
Carl

Comments

Post a Comment

Popular posts from this blog

ClassCastException: JAXB

Image
A particular Java application I co-developed leverages both SOAP/WSDL and REST web services.  We use maven to manage the build process of this application which has been in production for a few years now.  It's been around long enough to have moved from Java 5 to Java 6 and now Java 7 (with limited testing using Java 8).  We have also had the experience of initially including JAXB jar files with our application and dealing with the "endorsed" directory because JAXB versions were a bit of a moving target for a while. Now that JAXB is neatly included with Java as it should be so we no longer include it.  I thought all of this was behind us (and unfortunately somewhat forgotten) until recently when we added Jersey 1.17 to the application to call some newer REST services. When trying to connect to the server, my stack trace included this: Caused by: java.lang.ClassCastException: com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to com.sun.xml.internal.bin...
Read more

JDeveloper installation on Mac OS X Mountain Lion

Let's get the "why?" out of the way first - Personally I like to know what IDE's are alive and well for any for any Java development I might be doing especially if it's something new or something I have not done for a while. Currently NetBeans is my first choice.  Certainly Eclipse is a great standby for any Java development (and a whole lot of non-Java stuff for that matter).  I have tried to get into the in some circles extremely popular Intellij IDEA IDE but so far I am not a fan. JDeveloper , from Oracle, has an interesting history (I think back to my JBuilder days any time it's mentioned).  It still exists and I assume is well respected or at least used by those in Oracle shops because it does seem to integrate nicely with (or is at least aware of) all things Oracle. Recently I wanted to check out some functionality specific to JDeveloper and decided I needed to install it on a relatively new MacBook Pro running OS X 10.8.2 (aka Mountain Lion). ...
Read more

JNLP: note to self

Java security was a hot topic in 2013 and I think it will continue to get some attention as tooling catches up to the newer requirements.  Signing the JNLP for Java Web Start programs is now required. The Java Web Start maven plugin does not yet sign the JNLP file but there is an outstanding issue which I imagine will be resolved before too much longer. In the meantime, this blog entry  and this stack overflow question and answer  may be all you need to get your JNLP signed correctly. The way I read it, you have two choices. First you can create a template file which should be named APPLICATION_TEMPLATE.JNLP in src/main/resources/JNLP-INF and wildcards are permitted.  This is nice if you have the need to deploy your application from more than one server. The second method involves creating a file named APPLICATION.JNLP also in the src/main/resources/JNLP-INF folder.  This file must match the application's jnlp file exactly. Don't forget to mo...
Read more