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.

Bug 35918 - "Stop Make" in the build menu would be useful.
Summary: "Stop Make" in the build menu would be useful.
Status: RESOLVED DUPLICATE of bug 118572
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Thomas Preisler
URL:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2003-09-05 01:52 UTC by honglin
Modified: 2007-10-11 16:40 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description honglin 2003-09-05 01:52:09 UTC
Desc: 
     [reported by Seongbae Park; filed on behalf
of Gordon Prieur]

Per Seongbae, "since 'make' was started from the
menu, one would expect s/he could stop it in the
same menu."

Comments:
      Gordon: The problem with a stop make in the
build menu is that you can have several makes
going at once.

      Ivan: Does the "execution view" distinguish
between multiple makes?

      Gordon: Yes, but we need more work here...
I just tried 3 make jobs concurrently. The
execution view showed all 3 but I only had the one
"make" tab. It looked like it mingled output
(which is obviously a feature:-) but it did track
the 3 make jobs.
              
              The execution view was also
confusing because it just showed the icon followed
by "make" 3 times. Hard to know which one was which.
Comment 1 _ gordonp 2003-09-06 20:46:41 UTC
I'm against a "Stop Make" in the build menu. What I would like is:

    o Multiple makes (running concurrently) got separate tabs
    o Each make in the execution view had uniquifying information

Probably a post Rainier enhancement though.
Comment 2 _ gordonp 2003-11-04 15:26:21 UTC
Removed RAINIER keyword. It shouldn't be on any cpp issues. Its for
issues we (Ifdef team) don't own.
Comment 3 Nikolay Molchanov 2006-05-06 07:26:49 UTC
This is my opinion from my "user's point of view":
 Yes, if there is an ability to start the same build several times, while
the first one did not finish yet, it is not clear which build to terminate.
Probably, all of them. I think this is a bug, that IDE allows multi start
of the same build, and does not ask user. It seems better to tell the user
that previous build is not finished yet, and to provide the ability to stop
the previous build and to start a new one.
I think it is absolutely necessary feature: stop the build. Even if it is
implemented so, that it will stop all these "identical" builds, it is good.
Now, when we have projects, we should have menu item "Stop Build" (or
"Interrupt Build") in contextual menu for each buildable project, and this
menu item should be enabled if a build of this project is running.
And, by the way, "Stop Build" looks better than "Stop Make" to me, because
our builds are more complicated than just a single "make" execution. This
is not about the wording, it is about the implementation of this feature.
It is not enough to kill the top level "make" process, it is necessary
to kill *all* processes, involved in this build.
Comment 4 julieg 2006-09-13 23:39:38 UTC
Per Jean's request, the IZ should be fixed by FCS.
Comment 5 Thomas Preisler 2006-10-06 06:41:02 UTC
It is very unlike we will get this feature done in CND1. There is already one
way of doing this and that is to open the Runtime view and kill the build
process. It's hard to find but it is there...
Comment 6 julieg 2007-01-11 01:19:15 UTC
This feature should be included in CND 5.5.1.
Comment 7 Thomas Preisler 2007-01-16 21:57:32 UTC
yes, but it is not a p1. Downgraded it to p2.
Comment 8 Thomas Preisler 2007-10-11 16:40:06 UTC

*** This issue has been marked as a duplicate of 118572 ***