> I made the same mistake. I had a makefile that compiled things the way I > was compiling in C++. But that caused all java files to be compiled. > Just compile the changed class. If that class instatiates another objects > and their java file have changes, javac will compile them. Don't put the > dependencies in the makefile. > > Rob > -----Original Message----- > From: Kontorotsui [SMTP:[EMAIL PROTECTED]] > Sent: Friday, July 30, 1999 2:27 PM > To: Java Linux List > Subject: Working with many .java files > > > 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. > > Thanks for your advices. > > --- > Andrea "Kontorotsui" Controzzi - MALE Student of Computer Science at > University of Pisa - Italy - E-mail: [EMAIL PROTECTED] > My home page: http://www.cli.di.unipi.it/~controzz/intro.html > > > ---------------------------------------------------------------------- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] ---------------------------------------------------------------------- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]