This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Ran mac installer build from internal javafx /plugins mockup page. This pulls from Hovnivals Tools Installer latest build#63. The installer works but I was unable to start the IDE. received: Exception in thread "main" java.lang.NoClassDefFoundError: org/netbeans/Main Caused by: java.lang.ClassNotFoundException: org.netbeans.Main at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:316) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:288) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:374) lark-fitzgeralds-macbook-pro:bin larkfitzgerald$ This was probably caused by disabling the preview on mac.
After installation the NetBeans application does not contain jar files in the 'modules' folders (for example in the ./ide9/modules directory, ./javafx/modules, etc). It looks like that it is an installer issue.
please attach installation log (/var/log/install.log).
looks like the issue of the build system... /Users/hudson/releng/hudson/NBI-6.1-JAVAFX/installer/mac/newbuild/pack200.sh: line 13: 498 Trace/BPT trap pack200 -J-Xmx256m -g $f.pack $f [exec] chmod: /Users/hudson/releng/hudson/NBI-6.1-JAVAFX/installer/mac/newbuild/netBeans/baseide/build/netbeans/ gsf1/modules/org-netbeans-modules-html-lexer.jar.pack: No such file or directory [exec] Packing /Users/hudson/releng/hudson/NBI-6.1-JAVAFX/installer/mac/newbuild/netBeans/baseide/build/netbeans/ gsf1/modules/org-netbeans-modules-html.jar [exec] Error occurred during initialization of VM [exec] java.lang.ArrayIndexOutOfBoundsException: 4
Created attachment 65209 [details] install.log
Afaik build 65 is fine, please verify. Feel free to reopen if the issue would be reproduced in the future..
verified in build #65.