NetBeans infrastructure allows to have Attach-Debug history. The history items appears in the menu associated with Debug button on the main toolbar.
It would be great to have the the history associated with Run button on the main toolbar. It should work exactly the same as for Attach-Debug.

Means BuildExecutionSupportImpl would need to support multiple finished items in a LRU list so that the Run toolbar button could have a dropdown arrow next to it. (TBD if there should be some more keyboard-accessible version of this enhancement as well.) Probably not hard to implement but would require some sort of UI review.

please review the attached api change in projectuiapi module, it's enhancing the BuildExecutionSupport's Item interface to allow grouping per action triggered (see ActionProvider's constants)
the implementation then adds popup to the Run action's toobar icon and records all executed ant and maven project Run builds showing them in the list. Entries get removed when associated project gets closed or when the history list size is exceeded (currently 7 items hardcoded). Entries are not persistent across IDE sessions, but client code can persist it's own executions and call BuildExecutionSupport methods when really required.

We have used this API in Oracle Solaris Studio IDE (product, based on CND).
Everything works good, thanks a lot!
Just one question. The JavaDoc says that
ActionProvider.COMMAND_RUN
is the only supported action for now.
What should be done to support DEBUG actions as well.

Trying to use the functionality in NB launchers (there several history items may be connected to the single project) I faced a problem with inability to unregister an item which is no more valid. Could you please provide a way to somehow update the list?

(In reply to henk89 from comment #13)
> Trying to use the functionality in NB launchers (there several history items
> may be connected to the single project) I faced a problem with inability to
> unregister an item which is no more valid. Could you please provide a way to
> somehow update the list?
what exactly do you mean? how can the build executed become invalid? it's not possible to execute the same build anymore? why not just skip it when someone accidentally triggers it.

(In reply to Milos Kleint from comment #14)
> (In reply to henk89 from comment #13)
> > Trying to use the functionality in NB launchers (there several history items
> > may be connected to the single project) I faced a problem with inability to
> > unregister an item which is no more valid. Could you please provide a way to
> > somehow update the list?
>
> what exactly do you mean? how can the build executed become invalid? it's
> not possible to execute the same build anymore? why not just skip it when
> someone accidentally triggers it.
We implemented Run launchers for CND projects which allow several run commands for the single project. In case user deletes one of them we should remove the corresponding item from run history.

fine, file a separate low priority issue for it. in the meantime you should make sure that your history item properly recognizes the state and reports to the user when triggered.
closing this one as fixed