Feature/156 add scope to run config

[brianneoberson]

• created a "Default" run config which will be used for the actionable pitest runs
• fixed the issue with the editing of run config settings. The editor now notices changes and they can be applied.

[lheimbs]

I have a slight concern that users will add their custom class paths in the Default config then then wonder why they are gone after using some action...

[nikomall34]

I noticed that when I restart my IDEA, my run configuration persists, but the options I entered in the Gradle task and target classes are lost.

[brianneoberson]

I have a slight concern that users will add their custom class paths in the Default config then then wonder why they are gone after using some action...

I am afraid we won't have time to find and implement a solution for this until tomorrow. But this could be a small ticket for next sprint. We fixed the other requested changes.

[nikomall34]

Maybe a quick fix could be to make the default runconfig not editable? Or maybe write somewhere in the Default run config "Please don't change".

[lheimbs]

I've added a simple solution to disable the targetClasses field when it is the default run config. All other configs' fields are still editable.

[nikomall34]

Unfortunately, I can still edit the default run configuration. I can simply modify the targetClasses in the run configuration, and when I click on "run" the specified classes are executed.

[lheimbs]

Unfortunately, I can still edit the default run configuration. I can simply modify the targetClasses in the run configuration, and when I click on "run" the specified classes are executed.

Did you remove the old one? Because that one obviously doesn't have the attribute set to true.

Edit: Okay if one exists after first ide boot it doesn't have the attribute set and it is still editable, my bad. On it.

[nikomall34]

Ok works as expected!