Instead I issued the command during the compile time and then executed my program: $ javac -cp /Library/Java/Extensions/mysql-connector-java-5.1.29-bin.jar FirstExample.javaĪnd this is what I got. Now the above says you should include the classpath when you are 'executing' the program ( java -cp ~/Library/Java/Extensions/foo.jar Bar), but it did not work for me. I dropped the jar file in the Library/Java/Extensions folder and restarted my machine. I spent some time trying to figure it out and found the solution.

but I wanted to run my small database program at the command line but I needed mysql-connector-java-5.1.29-bin.jar in the class path to do so. In addition, solving bugs in Eclipse for Mac OS X is relative slow as compared to other platform. There is a need to come out with a simple and systematical trouble-shooting to isolate the cause of failure in activation for newbie in Java development. (system-level or user-level, depending which directory is used). Very often, it worked on the first installation and failed on the subsequent activation. Will be available to all applications run under the respective scope Items placed in either of theseĭirectories do not need to be named in an application's classpath and ~/Library/Java/Extensions directory can be used for user-level The /Library/Java/Extensions directoryĬan be used for additional jar files or JNI libraries that need to be Lib/ext directory, developers should not directly modify it for the $JAVA_HOME/lib/ext directory within a JDK installation to store Java software on other platforms often makes use of the This breaks my app.īut if you really want to do this: According to Apple's docs: Sometimes there is an older version of the same JAR file in the appropriate Extensions folder. It relies on having a specific recent version of a JAR file (for JFreeChart). Here's why: Other apps will break, because those JAR files will be loaded for every Java app.

Java for mac os x 10.2