Kontorotsui wrote:
>
> Hello,
> so far I worked using the good old xemacs + Makefile combo.
> As soon as my application grow and more classes are created, I'm beginning to
> feel the weight of a full scale compilation (like 20 seconds now, but it's
> increasing fast) even after I change 1 line of code in 1 class.
>
> Now, I don't think there is a way to recompile only the class I changed, like
> we did in C, is this correct? I remember someone who wrote, weeks ago, about a
> tool that can check the classes and make the compiler work only on the sources
> that really need to be compiled again, but maybe I'm mistaken.
>
> How do you manage a project with so many .java files, say more than 100?
> I can't believe I'll be forced to wait 3 minutes of compilation (on a 128Mb
> K6-2 350Mhz) every time I forget a ; or mistype a variable.
We use make to great advantage. Our system has ~1000 java files and
make reduces compile time dramatically. ( We use jikes, too, so that
helps. ) Using production rules, make will only compile a java file
when the timestamp on the .java file is later than the timestamp on the
.class.
--
Justin Lee | It's not the weight of the stone that's holding you down.
JEDI | It's the way it fascinates your mind. -- Tourniquet
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
