RunManagerListeners registered with RunManagerImpl#addRunManagerListener(RunManagerListener) are not notified when a configuration is modified from the GPRbuild tool window. This is probably due to the fact that all configuration data (gprbuild arguments and scenario variables) are stored and modified entirely on the plugin side, and therefore the run manager has no idea that a configuration has been changed when the plugin defined methods GPRbuildConfiguration#setGprbuildArguments(String) and GPRbuildConfiguration#setScenarioVariables(Map) are called.
One possible solution is to manually implement configuration change events/listeners for GPRbuild configurations only, by maintaining a set of listeners in GPRbuildConfigurationManager and notifying them whenever the custom GPRbuild configuration modification methods are called.
RunManagerListeners registered withRunManagerImpl#addRunManagerListener(RunManagerListener)are not notified when a configuration is modified from the GPRbuild tool window. This is probably due to the fact that all configuration data (gprbuild arguments and scenario variables) are stored and modified entirely on the plugin side, and therefore the run manager has no idea that a configuration has been changed when the plugin defined methodsGPRbuildConfiguration#setGprbuildArguments(String)andGPRbuildConfiguration#setScenarioVariables(Map)are called.One possible solution is to manually implement configuration change events/listeners for GPRbuild configurations only, by maintaining a set of listeners in
GPRbuildConfigurationManagerand notifying them whenever the custom GPRbuild configuration modification methods are called.