To reproduce:
1. make sure compiler is configured to run in background
2. create a run configuration that launches make before run
3. start lengthy compilation
4. while the compilation is in progress launch the run configuration.
The effect is that second "make" tab is added immediately causing the previious make to close (there will be a question whether you would like to close the first tab).
Eugene Zhuravlev - 29 May 07 18:19 To reproduce:
1. make sure compiler is configured to run in background
2. create a run configuration that launches make before run
3. start lengthy compilation
4. while the compilation is in progress launch the run configuration.
The effect is that second "make" tab is added immediately causing the previious make to close (there will be a question whether you would like to close the first tab).
I think I found the problem: check out the CompileDriver.startup() method: and the synchronized block inside it: the CompierTask.start() must not be asynchronous (see the invokeLater inside it).
Eugene Zhuravlev - 29 May 07 18:26 I think I found the problem: check out the CompileDriver.startup() method: and the synchronized block inside it: the CompierTask.start() must not be asynchronous (see the invokeLater inside it).
1. make sure compiler is configured to run in background
2. create a run configuration that launches make before run
3. start lengthy compilation
4. while the compilation is in progress launch the run configuration.
The effect is that second "make" tab is added immediately causing the previious make to close (there will be a question whether you would like to close the first tab).