Community
Participate
Working Groups
It would be nice if the batch compiler (specifically the one that can be used by an Ant script) would act more like the Java Builder in eclipse. As is, the batch compiler will compile a source file and all source files it depends on. I want to be able to turn this "feature" off. Basically I have the following scenario... I need to compile Project1/src to Project1/bin I need to compile Project2/src to Project2/bin Project1/src has source files that depend on Project2/src source files. When Project1/src is compiled, the current implementation successfully compiles Project1/src to Project1/bin, but is also compiles Project2/src to Project1/bin. I have a patch that fixes this by adding a CompilerOption.
Created attachment 26090 [details] Addition of skipReferences compiler option This patch adds a compiler option to allow "not" compiling a source file's references/dependencies.
The java builder in Eclipse recompiles dependent types if necessary. So the batch compiler and the java builder have a similar behavior. Not compiling the dependants is error prone.
True, I agree that not compiling dependents would be very error prone. I just really like the feature of the Java Builder in Eclipse that allows for "multiple output" locations. How is this currently accomplished? Because with the batch compiler, everything gets compiled to one directory.
Yes, the batch compiler doesn't support multiple output folders. But this is a different issue than the one related to the compilation of dependant classes. So what you really want is the support for multiple output folders in the batch compiler.
Having a batch incremental compiler is interesting, for the request for multiple output folders, this is a separate issue which would deserve its own bug report.
(In reply to comment #5) > ... for the request for > multiple output folders, this is a separate issue which would deserve its own > bug report. Entered https://bugs.eclipse.org/bugs/show_bug.cgi?id=146554 to this effect.