Re: Incremental Java Compile
On 02-05-2010 17:08, Joshua Maurice wrote:
On May 1, 7:38 am, Lew<no...@lewscanon.com> wrote:
Joshua Maurice wrote:
So, I post here because I feel better prepared to discuss this
subject. I still disagree that "build from clean" is the correct
answer. That would make our product's build still around ~25 minutes
for just the Java compilation of around ~20,000 source files (and
growing). There must / should be something better. Separation
translation units make so much sense. I just wish Java had them.
What, you never heard of JAR files?
There's no excuse for "build clean" having to touch all 20K files.
And what if all of the code is under active development, aka new
features are being added to each layer on a weekly basis?
Still not a good excuse.
Each team/stream/whatever you call it should work on their own
component and a stable binary release of all other components.
And what if a large portion of that Java code is generated from a
model file to facilitate serialization between C++ and Java? Thus a
change to a single file would require recompiling a large amount of
generated "interface" files, which theoretically touches a large
portion of the 20,000 Java files.
Structure things better.
With a good OO model a series of related changes should not
require changes in "a large portion of 20000 Java files".
Arne