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.
|Summary:||7.2 beta only allows a single instance of a Java project to run, can no longer run multiple instances|
|Component:||Generic Projects UI||Assignee:||Tomas Stupka <tstupka>|
|Severity:||normal||CC:||chunkyks, dudy, JorisW, mmirilovic, psomol, tzezula|
|Issue Type:||DEFECT||Exception Reporter:|
|Bug Depends on:|
Description johnpm 2012-05-26 00:50:30 UTC
Upgraded from 7.1.2 to 7.2 beta but can now only run one instance of my Java project, Run Project (F6) is disabled when the first instance starts. In every previous version of the IDE (at least back to V4) could run multiple instances at the same time.
Comment 1 johnpm 2012-05-26 17:56:14 UTC
The run command gets re-enabled on switching to another file in the editor.
Comment 2 Marian Mirilovic 2012-05-27 15:06:38 UTC
Hmm, it works for me in NB Dev 20120524, JDK 7u4, Ubuntu 11.10 x64
Comment 3 Jiri Prox 2012-05-28 08:03:36 UTC
I can reproduce it, when I start Anagram Game and switch back to IDE, the Run Project (F6) is disabled, but after switching the file or transferring cursor to project view (and back) it is enabled again Product Version: NetBeans IDE 7.2 Beta (Build 201205031832) Java: 1.7.0; Java HotSpot(TM) Client VM 21.0-b17 System: Windows 7 version 6.1 running on x86; Cp1250; en_US (nb) User directory: C:\Users\jprox\AppData\Roaming\NetBeans\7.2beta Cache directory: C:\Users\jprox\AppData\Local\NetBeans\Cache\7.2beta
Comment 4 Jesse Glick 2012-05-29 21:15:35 UTC
Intentional. *** This bug has been marked as a duplicate of bug 206208 ***
Comment 5 twolf2919 2012-05-31 17:21:59 UTC
I'm not sure if the procedure is proper, but I'm re-opening this bug on account that it takes away a convenience feature - the ability to easily "Run" multiple instances of the current project. I do that all the time to, for instance, compare two application outputs based on different inputs. I realize that I can get around this bug by right-clicking on the project node and hitting "Run" from there or, as it turns out (found this by pure accident) - click anywhere to re-enable it. But that's less convenient. And I, as an end-user, can't really see the benefit for you doing so - are you trying to cater to total bone heads that might otherwise accidentally hit "Run" twice? From a developer's perspective, I can imagine that the reason might be that it was simply easier to implement on all the buttons rather than just the "Build" ones - which is what this bug said to fix. I realize that this is minor and you can choose to ignore my comments, but do you honestly think that disabling "Run" like this is a net benefit to users? Like I said above - I had no f'in clue why the "Run" button was disabled....I hunted around for a way to get my second application instance up and found "Run" on the project node - so for a bit I thought that was the only other way now....then I just happened to notice that when I clicked in other NB windows - after the first instance was started - that the "Run" button had magically re-enabled....that's not intuitive.
Comment 6 Jesse Glick 2012-05-31 21:41:05 UTC
(In reply to comment #5) > I can get around this bug by right-clicking on the project node > and hitting "Run" from there Yup. Just the global (potentially main-project-sensitive) actions are adjusted this way. > are you trying to > cater to total bone heads that might otherwise accidentally hit "Run" twice? Not boneheads necessarily, but anyone with a bouncy mouse, since parallel Ant builds can clobber one another. Just implementing the requested feature. I do not have much personal opinion either way, leaving it to UI. Please address comments to the original bug #206208, not here. *** This bug has been marked as a duplicate of bug 206208 ***
Comment 7 Marian Mirilovic 2012-06-08 09:12:37 UTC
*** Bug 213791 has been marked as a duplicate of this bug. ***
Comment 8 chunkyks 2012-06-29 17:29:37 UTC
I'm making one more attempt to re-open this bug. As a solution to the original bug, about builds clobbering each other, disabling the *build* button seems perfectly reasonable. But in the process, I and others have lost a feature that we actively use. Mostly I find it frustrating when energy is invested developing code whose sole purpose is to *remove* a feature I use daily.
Comment 9 Ervilha 2013-04-02 10:15:19 UTC
Please rollback that "fix" it really makes no sense... Its so annoying have to click on the project files to be able to run another instance, special when you are developing client/server applications where you need to run multiple clients. You can keep the grayed-out button, but at least enable the F6 Short Key please.
Comment 10 dorknexus 2013-10-22 23:22:13 UTC
This behavior doesn't make sense for projects that contain multiple main methods.
Comment 11 PeterSorg 2014-01-21 17:53:36 UTC
Can't understand what's good for. Just annoying.
Comment 12 chunkyks 2014-10-30 05:13:23 UTC
I am changing this issue to Netbeans version 8.0.1 as it is still a major issue for my workflow in the current release