Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 338015 - Project builder configuration dialog should warn about launching in the background
Summary: Project builder configuration dialog should warn about launching in the backg...
Status: CLOSED DUPLICATE of bug 99038
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-23 15:04 EST by Michael Rennie CLA
Modified: 2013-08-06 14:02 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Rennie CLA 2011-02-23 15:04:31 EST
Version: 3.7.0
Build id: I20110222-0800

When you create a new Ant-based project builder, you can specify that you want it to launch in the background on the Builder Options tab. Doing so, and having the option on the JRE to launch in the same JRE in the workspace results in the following exception when you try to build the project:

org.eclipse.core.runtime.CoreException: Ant build C:\Users\mrennie\workspaces\runtime-3.6.x\TestBuilders\builder.ant already in progress. Concurrent Ant builds are possible if you specify to build in a separate JRE.
at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:172)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:695)
at org.eclipse.core.externaltools.internal.model.ExternalToolBuilder.launchBuild(ExternalToolBuilder.java:181)
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:203)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:344)
at org.eclipse.ui.actions.GlobalBuildAction$1.run(GlobalBuildAction.java:179)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Although it is considered bad form to make launch configuration tabs know about the settings on other tabs, it would be better to validate this combination of options rather than blow up during a build.
Comment 1 Michael Rennie CLA 2013-08-06 14:02:53 EDT

*** This bug has been marked as a duplicate of bug 99038 ***