#10 Exception during launch configuration migration

[Mirko Raner]

Under certain circumstances the following exception is thrown:

org.eclipse.core.runtime.CoreException: File /nl.dslmeinte.xtext.conditional/.externalToolBuilders/conditional mwe2 builder.launch is read-only.
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.writeNewFile(LaunchConfigurationWorkingCopy.java:365)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave0(LaunchConfigurationWorkingCopy.java:245)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.access$0(LaunchConfigurationWorkingCopy.java:233)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy$1.run(LaunchConfigurationWorkingCopy.java:210)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave(LaunchConfigurationWorkingCopy.java:213)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave(LaunchConfigurationWorkingCopy.java:170)
at org.eclipse.core.externaltools.internal.registry.ExternalToolMigration.migrateRunInBackground(ExternalToolMigration.java:362)
at org.eclipse.core.externaltools.internal.model.ExternalToolBuilder.launchBuild(ExternalToolBuilder.java:180)
at org.eclipse.core.externaltools.internal.model.ExternalToolBuilder.doBuildBasedOnScope(ExternalToolBuilder.java:169)
at org.eclipse.core.externaltools.internal.model.ExternalToolBuilder.build(ExternalToolBuilder.java:88)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:282)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:363)
at org.eclipse.core.internal.resources.Project$1.run(Project.java:545)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:524)
at org.eclipse.core.internal.resources.Project.build(Project.java:123)
at net.sf.ebuilder.Ebuilder$2.launch(Ebuilder.java:332)
at net.sf.ebuilder.utilities.SynchronizedLaunch.<init>(SynchronizedLaunch.java:74)
at net.sf.ebuilder.Ebuilder$2.<init>(Ebuilder.java:327)
at net.sf.ebuilder.Ebuilder.buildIndividualProjects(Ebuilder.java:327)
at net.sf.ebuilder.Ebuilder.buildAll(Ebuilder.java:286)
at net.sf.ebuilder.Ebuilder.build(Ebuilder.java:203)
at net.sf.ebuilder.Ebuilder.earlyStartup(Ebuilder.java:137)
at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87)
at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.Workbench$59.run(Workbench.java:2409)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

The "migration" that is being attempted here has to do with converting between the legacy ATTR_RUN_IN_BACKGROUND attribute and the ATTR_LAUNCH_IN_BACKGROUND attribute that was introduced in a later version of Eclipse. A mismatch of these attributes could also be the reason why certain builders sometimes seem to get triggered simultaneously.