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.
In Windows 7, when I pin NetBeans shortcut to the taskbar, clicking the NetBeans shortcut from the taskbar will initially cause the icon to be highlighted, but then it creates a second process icon in the taskbar for the actual application process, contrary to the standard behavior of Windows 7 applications. I assume this aberrant behavior may have something to do with the netbeans.exe launcher creating a separate javaw process. This may not be a big thing, but it is annoyingly inconsistent with standard Windows 7 behavior. Moreover, fixing this issue would reduce unnecessary clutter in the developer's taskbar. Other Java applications executed directly from javaw.exe do not experience this behavior. For example, I have an Java application that I use regularly. My Windows shortcut is set up with the following properties: Target: C:\Windows\System32\javaw.exe -jar C:\XQDev\bin\xqdev.jar Start In: C:\XQDev\ Icon: C:\XQDev\bin\xqdev.ico I can pin this shortcut to the Windows 7 taskbar and after executing it, I can continue to use the same taskbar icon to switch to the app as normal, without a separate process icon being added to the taskbar.
http://www.strixcode.com/sevenbeans/
Gimp, Inkscape, ArgoUML and MySQL Workbench will all work properly as well. The extra icon is not a big thing, but it is annoying when you have a number of tasks open that developers normally do during the day.
Assigned to new owner.
This has been solved as a bug (http://netbeans.org/bugzilla/show_bug.cgi?id=199782 ). The solution was creation of 64-bit launcher. Will be included in 7.2. This issue appears when running 32-bit NB on 64-bit JVM and conversely 64-bit NB on 32-bit JVM. Simply you cannot start 32-bit process from 64-bit one... That's why javaw is started. In 7.2 there will be two launchers 32 and 64-bit. You should choose one of them due to JDK version. Also while installation the correct one is chosen due to selected JDK.
Sorry, bad link attached. The correct one: http://netbeans.org/bugzilla/show_bug.cgi?id=178273