Page History

...

This Project Action can be then invoked programmatically, apart from the project UI itself, by a LSP client, too.

 Since the action can be seen as a replacement for traditional Run (depending on project characteristics and user's preferred workflow), it should be configurable as the  default Run action, responding for

• ActionProvider.COMMAND_RUN,
• ActionProvider.COMMAND_RUN_SINGLE.

 Need to define how an (abstract) "Run" action can be remapped to a different action ("run-continuous") defined in nbactions.xml. 

Display Action in the UI

Neither Gradle or Maven support adding technology-specific actions in the project UI. Even if the action is defined in nbactions.xml, it will not appear anywhere in the popup menu, except for custom actions (having CUSTOM- prefix in their action name; maven only). In this case, I would like to display the Continuous Run action alongside the Run and Debug.

• Gradle supports the --continuous flag from version 4.0.x (7 / 2017), so it seems pretty safe to add that action unconditionally to the project menu. There are some limitations documented, the action could warn the user for the 1st time the action is used, if it encounters such an environment.
• The action should not be present for other than micronaut projects (those which contain MN plugin) in Maven. 

 Need to define  a representation of such configuration in the UI. An alternative would be a menu item that

• executes on click,
• can display a submenu which contains
  • Run once
  • Run continuous
• the new state would be remembered