| Summary: | Exception in thread "main" java.lang.NoClassDefFoundError: apple/laf/CoreUIControl | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Harry Erwin <herwin> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | Michael_Rennie, remy.suen |
| Version: | 3.6.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Harry Erwin
How is this problem related to Eclipse exactly? Does the program run if you launch from the command line? The same problem seems to occur with anything involving javax.swing. On the other hand, these programs run fine if launched from a jar file or from the command line. (In reply to comment #2) > The same problem seems to occur with anything involving javax.swing. On the > other hand, these programs run fine if launched from a jar file or from the > command line. What if you take the exact string from Eclipse and launch that from the command line? http://wiki.eclipse.org/Graphical_Eclipse_FAQs#How_do_I_check_for_the_command_line_invocation_that_Eclipse_used_to_launch_an_application.3F (In reply to comment #3) > (In reply to comment #2) > > The same problem seems to occur with anything involving javax.swing. On the > > other hand, these programs run fine if launched from a jar file or from the > > command line. > > What if you take the exact string from Eclipse and launch that from the command > line? > http://wiki.eclipse.org/Graphical_Eclipse_FAQs#How_do_I_check_for_the_command_line_invocation_that_Eclipse_used_to_launch_an_application.3F It dies. Here's the launch string /System/Library/Frameworks/JavaVM.framework/Versions/1.5/Home/bin/java -Dfile.encoding=MacRoman -Xbootclasspath:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/classes.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/ui.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jsse.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/jce.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/charsets.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/ext/apple_provider.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/ext/dnsns.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/ext/localedata.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/ext/sunjce_provider.jar:/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/lib/ext/sunpkcs11.jar -classpath /Users/herwin/Documents/workspace/Wessex/bin:/Applications/eclipse/junit4.5/junit-dep-4.5.jar:/Applications/eclipse/junit4.5/junit-4.5.jar:/Applications/eclipse/junit4.5/junit-4.5-src.jar org.dherwin.wessex.WessexController Let me correct the version... (In reply to comment #4) > Let me correct the version... That worked. The message is that if you're upgrading to Java 6, you need to chase up the VM in the preferences... When you move from Java 5 to Java 6, you have to fix the Eclipse preferences. Blame it on operator headspace. |