It is intentional. See nbui mailing list and issue 75465.

How comes the processes node is already unconditionally removed, yet the
replacement mechanism is only available on special hidden option?

Seems that more people were used to it :). Me as well. On the otherside once
75465 is implemented....

Ok it's intentional, but I would expect at least some discussion or
informational email. Why do we do UI Review for small UI changes if the change
like this is not discussed/reviewed ? 

Jesse, 
please revert this change for now (we are testing M2 build this week) and please
implement issue 75465 next week.

But I still do not understand why the proccess node is removed. The issue 75465
is about stop button in output window. And I think output windows are not a good
indicator of running processes - they can be closed.

Reverted in core/execution/src/org/netbeans/core/execution/resources/layer.xml 1.27.

Re. reason for removal of node: only really useful for Ant processes AFAIK, but
in fact the Stop Process action for an Ant process in this node is inferior to
the specialized Build | Stop Building as it does not know anything about Ant and
just tries to kill the thread.

Re. output windows being closed - yes, they can be, but Stop Building is still
accessible in this case. Also it is planned to have a progress component running
for Ant processes, once UI issues re. indeterminate progress bars can be
resolved (needs API change); these would also always be visible so long as the
process were running, regardless of whether an OW tab is closed.

I support removing the process node but I agree that it should be communicated before making the 
change. The right way how to terminate running application is:

- Stop button in output window toolbar. It only works until the user closes the output.
- Main menu item. Currently we have "Build | Stop Build/Run".
- The new process window associated with global progress indication (Window | Processes). Currently it 
doesn't show up running applications, but it should in the near future, AFAIK.

I'm not happy for such solution. I think most of users use Processes node to
kill running java processes. Now if I want to kill some processes I have to go
through menu to Build | Stop Build/Run - here I really do not understand why it
is under Build menu and I would never find it there.
The action opens some !modal! dialog where I can kill the processes. I think it
is too complicated and too covered for such elemental things like running
processes in ide.

People use the Processes node *now* because it exists and the replacements are
not all here yet.

Location of menu item - applies to either builds or runs. Could equally be under
the Run menu, would be just as arbitrary. Or could (confusingly) be in both
places. Not possible in all cases to differentiate, I think, since the
differences are only conventional. Anyway when there is an OW button that will
probably be the most discoverable option and this menu item will be mostly for
KB accessibility.

Modal dialog - dialog for the menu item is only opened in case there is >1
process running, in which case you can pick the one(s) to stop. (As of
yesterday, the labels are always distinct.) Could easily be changed to create a
submenu in this case if anyone prefers that.

I'm curious what you mean by: "As of yesterday, the labels are always distinct."

Re. last comment: minor issue noted on nbui. If you run the same app multiple
times, previously you would get a lot of tabs "Foo (run)" which you would have a
hard time telling apart, esp. in Build | Stop Building. Now they will be
labelled "Foo (run)", "Foo (run) #2", "Foo (run) #3", etc.

IMHO from Build menu should be possible to stop only building/compiling
processes and in Run menu only processes possible to start from Run menu (debug,
run, test ...).
But I think Window | Processes will be the most used way to stop proccesses.

It's not possible to reliably differentiate "build" from "run" processes in a
way that will work for freeform projects and Ant projects of any sort with
customized build scripts. It may be possible to guess correctly in most cases.
But at any rate the action would do exactly the same thing whatever its label.

I expect that the stop button in the output tab would become the most used way
to stop builds, due to its visibility, but this is just a guess.

v

But see issue #83313.