Disable splash screen on your Netbeans Application
Just add run.args.extra=--nosplash to the project.properties file
Just add run.args.extra=--nosplash to the project.properties file
If you are getting javax.jnlp.UnavailableServiceException from javax.jnlp.ServiceManager.lookup() or if javax.jnlp.ServiceManager.getServicesNames returns null you must be aware that those call only return useful thing when you run your code from the Java Web Start environment. It’s not enough to include the jnlp.jar or javaws.jar in the classpath. For example to make it work from Netbeans you must enable WebStart in the project and Set Configuration to WebStart.
It seems that is imposible to type the ˜ symbol (named also tilde,squiggle,twiddle,not,approx,wiggle,swung,dash,enyay,sqiggle) in Netbeans with a Swedish keyboard at least. It seems that it’s a long known java bug (bug 6353098, bug 6253172). At least I can use the Alt+126 code to type it.
I’m new in NetBeans and today I’ve been struggling a couple of hours with the simple task of attaching the source code for an external JAR (NetBean Library Wrapper Module). I’ve been trying to find in google how to do it without success until I reached this post in the netbeans-users mailing list. Then I realized that I should been looking into the NetBeans Help first. The entry at Help -> Help contents -> Java Applications -> Debugging Applications -> Attaching Source Code to a JAR File explains how to do it. ...
My first try with the Netbeans Paint Application tutorial didn’t work as expected. For some reason I got this stack trace when I tried to run it: java.lang.IllegalStateException: Module was supposed to be OK: StandardModule:org.netbeans.modules.projectuiapi jarFile: C:\Program Files\NetBeans 6.0\ide8\modules\org-netbeans-modules-projectuiapi.jar at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1087) at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1104) at org.netbeans.ModuleManager.maybeAddToEnableList(ModuleManager.java:1104) at org.netbeans.ModuleManager.simulateEnable(ModuleManager.java:1048) at org.netbeans.core.startup.ModuleList.installNew(ModuleList.java:379) at org.netbeans.core.startup.ModuleList.trigger(ModuleList.java:341) at org.netbeans.core.startup.ModuleSystem.restore(ModuleSystem.java:275) at org.netbeans.core.startup.Main.getModuleSystem(Main.java:171) at org.netbeans.core.startup.Main.start(Main.java:322) [catch] at org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:110) at java.lang.Thread.run(Thread.java:619) I managed to solve it although I don’t really know the cause. ...
It took a while to find this entry describing how to include the Netbeans APIs source code. In short, you have to download the actual sources (the link in Geertjan’s Weblog is outdated) at http://download.netbeans.org/netbeans/6.0/final/zip/ (file netbeans-*-platform-src.zip) and then link that zip file to the platform in the platform manager. Make sure that the path doesn’t contains whitespaces (it didn’t work for me). To access the Netbeans Platform Manager just do Tools -> Netbeans Platforms ...
I’m following the Netbeans Platform Porting tutorial and the NotifyDescriptor was not been recognized by the IDE. I found out that you must add the Dialogs API to the Libraries. Just right-click Libraries and then select “Add module dependency”. In the “Add Module Dependency” dialog just type NotifyDescriptor on the “Filter” field and it automatically select the Dialog API for you.
After struggling with Netbeans 6.0 Ruby a little bit I finally found why my puts statement are not working properly. It’s due to the following reported bug.(Vote for this bug!!) Also noted in the RubyTodo page from Netbeans wiki. This problem appears when using native ruby with netbeans instead of jruby. My workaround is using log4r instead for print statements. UPDATE: It has been fixed in the latest version of the ruby module. I had to download the prebuilt ruby cluster from http://deadlock.nbextras.org/hudson/job/ruby/ and install it using the following instructions because the ruby module version found in the update center was not fresh enough but today I checked again and version 0.39 is available from the Update Center as well.