No ALE Run Configuration created when launching ALE through the contextual menu shortcut

[echebbi]

Expected behavior

When ALE is launched through the contextual menu shortcut a new ALE launch Run Configuration should be created. The main benefit is that we could easily run a same script multiple times in a row by just typing Ctrl+F11 or searching a previously launched script through the Run History.

Note: what I mean by "contextual menu shortcut" is:

• Right clicking on a .dsl file > Run As > ALE launch

Current behavior

No Run Configuration is created. Hence, we have use the contextual menu each time we want to launch the same script or manually create a dedicated Run Configuration.

Solution

To solve this, the usual algorithm is (within a launch shortcut instance):

1. Retrieve the template of the desired Launch Configuration
2. Create a new Launch Configuration instance based on the template
3. Set the Launch Configuration's attributes
4. Run the Launch Configuration

For example:

public class LaunchShortcut implements ILaunchShortcut {

    @Override
    void launch(ISelection selection, String mode) {
        ILaunchManager manager = DebugPlugin.getDefault().getLaunchManager();
        ILaunchConfigurationType type = manager.getLaunchConfigurationType(AleRunConfiguration.ID);
        ILaunchConfiguration[] configurations = manager.getLaunchConfigurations(type);

        // Create a new launch configuration

        String baseConfigurationName = configurationNameFor(dslFileName);
        String launchConfigurationName = availableLaunchConfigurationName(baseConfigurationName, configurations);
	
        ILaunchConfigurationWorkingCopy workingCopy = type.newInstance(null, launchConfigurationName);        
        workingCopy.setAttribute(AleRunConfiguration.MODEL_FILE, ...);
        workingCopy.setAttribute(AleRunConfiguration.DSL_FILE, ...);
        ILaunchConfiguration configuration = workingCopy.doSave();
		
        // Run the new launch configuration
        configuration.launch(ILaunchManager.RUN_MODE, null);
    }

}

[dvojtise]

about calling the creation of the launch conf when performing a run
the relevant code is here in GEMOC: https://github.com/eclipse/gemoc-studio-modeldebugging/blob/641a6ac6db61c0c84d98df07b19647225a9caf75/simulationmodelanimation/plugins/org.eclipse.gemoc.dsl.debug.ide.ui/src/org/eclipse/gemoc/dsl/debug/ide/ui/launch/AbstractDSLLaunchConfigurationDelegateUI.java#L196

then the creation of the appropriate launch conf with default parameters is done in the implementation sub classes https://github.com/eclipse/gemoc-studio-modeldebugging/blob/master/simulationmodelanimation/plugins/org.eclipse.gemoc.dsl.debug.ide.sirius.ui/src/org/eclipse/gemoc/dsl/debug/ide/sirius/ui/launch/AbstractDSLLaunchConfigurationDelegateSiriusUI.java or https://github.com/eclipse/gemoc-studio-modeldebugging/blob/641a6ac6db61c0c84d98df07b19647225a9caf75/framework/execution_framework/plugins/org.eclipse.gemoc.executionframework.engine.ui/src/org/eclipse/gemoc/executionframework/engine/ui/launcher/AbstractSequentialGemocLauncher.java#L226