| Concurrent Ant builds, eclipse.incrementalbuild, launch configurations [message #313667] |
Wed, 21 March 2007 23:08 |
Eclipse User |
|
|
|
Hi,
I am working on a J2EE project where we use RAD 6.
Our developers are using a script called rebuildAll.xml which is started
by a launch configuration at workspace level.
This script invokes a number of Ant tasks which are unproblematic.
The launch configuration is defined to run in the Eclipse VM.
The problematic ant task is eclipse.incrementalbuild.
We are also using builders which are tied to projects.
Due to the existence of rebuildAll.xml and to the fact that it uses
eclipse.incrementabuild, we are forced to define all the project level
ant builders to run outside of the eclipse VM.
I suppose the best practice would be to scrap this rebuildAll.xml and to
tie all build tasks to projects, at which point we could redefine our
builders to run in the Eclipse VM.
I was also wondering whether eclipse.incrementalbuild when it invokes
directly or indirectly project level ant builds should not overcome the
rule that parallel ant builds are forbidden.
In the case of Ant based project level builders, what really gets
started is not a concurrent ant build, rather a nested ant build.
To my opinion this should be supported.
Should I open a bug report in Bugzilla to ask that ?
Best regards,
Antoine
|
|
|
Powered by
FUDForum. Page generated in 0.06062 seconds
Home