Community
Participate
Working Groups
I am using ant v1.6.5, and I simply add incremental="true" to my ant iajc task to attempt to use incremental compilation. The first compile appears to complete fine as I see: [iajc] press enter to recompile, r to rebuild, q to quit: as part of the ant processing. However, if I hit enter, or r, or q, I do not see the [iajc] press enter to recompile, r to rebuild, q to quit: line again informing me that that compilation attempt is completed and iajc awaiting the next request. This is not consistent with the documentation I have read. I also don't see anything in bugzilla noting this type of behavior. Andy Clement noted that this is "not a commonly used feature". I am left to wonder why that is the case. Does a non-incremental compile have reasonable response if only one java source file is changed in a large (say greater than 1000 classes) project? If so, I believe it would be of value to the community to update the documentation (Developer guide, development environment guide, etc.) in this regard to properly inform the reader as to what compilation approach is considered best practice under what conditions.
To repeat my reply on the list: To run ajc incrementally with Ant, the incremental tagfile option was developed to work around problems piping input and output through Ant, esp. when forking, so for now use the incremental tagfile option discussed in the iajc ant task documentation. The tasks were written for Ant 1.5.x but Ant pipes were updated around 1.6.1 (I think). I tried unsuccessfully last week to use the 1.6.5 API's, as stdin was not piped to the task even after setting up the pipes. todo...