> From: Moses DeJong <[EMAIL PROTECTED]>
> In Java the path
> name of the file defined what package it should be inside of.
NO! It's the package clause _inside_ the source file that defines
which package the class belongs to.
Whether the source file is in a directory hierarchy match
>
> 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.
Go to http://alphaworks.ibm.com
download and install jikes
[elof@hugin HEII
Yes, point 1 is correct. I use JDE with emacs and when I'm working on a
file, I just do ctrl-cvc to compile that file. It works really nice.
There really should be a better way to do projects though without using a
fast compiler like jikes as a crutch for dealing with large projects.
JBuilder
Thank you all for the many advices and the big discussion.
I sorted out this strategy:
1) If I change only a class because I edit the java file to add a ; I forgot, I
compile by using javac onlythisclass.java
2) If I change a lot, I compile with jikes
3) Since javac does better optimization
>Are you suggesting that I could do something like this:
> find . -name \*.java -print | xargs jikes ++
The principle works fine for me, although you'll eventually hit a
command line argument length! The nice thing is you can probably make
a generic Java makefile that works with any code.
You c
>Actually, I'm pretty sure Jikes has built in automatic dependency
>checking.
It might, but I wouldn't trust it. And in my code, static dependency
checking doesn't work - I'm routinely loading things dynamically.
>Try comparing the compile time for a "make clean" to a "make" (after
>changing a f
On Sat, 31 Jul 1999, Chris Kakris wrote:
> Chris Abbey wrote:
> >
> > A couple people mentioned that javac will recompile any classes referenced
> > by what you compile and recompile them if they're newer... true, but DON'T
> > RELY ON THAT to save you: it misses the opposite link. Say for examp
Chris Abbey wrote:
>
> A couple people mentioned that javac will recompile any classes referenced
> by what you compile and recompile them if they're newer... true, but DON'T
> RELY ON THAT to save you: it misses the opposite link. Say for example you
> have a static final boolean, and you change
OK, there was a lot of discusion about jikes on this thread, and rather
than post a bunch of little comments on each of the off shoot threads I'll
bundle it all up here
Riyad didn't miss anything, jikes can do a hell of a lot of files in the
blink of an eye. The bigest reason is that it is wr
Actually, I'm pretty sure Jikes has built in automatic
dependency checking.
Try comparing the compile time for a "make clean" to a "make" (after
changing a few non-critical source files)
Admittedly, I haven't pored over the source code or anything, but I
thought I read somewhere that it does it
>Granted I don't know much about Jikes but 280 files in 5 seconds
>amI missing someething?
Jikes is really, really fast. Being on all local disk (NFS) makes a
huge difference. And I'm on fast machines - a 500 MHz Pentium III now,
I think.
>Are you sure that jikes isn't just skipping over
Granted I don't know much about Jikes but 280 files in 5 seconds
amI missing someething?
Are you sure that jikes isn't just skipping over files that don't need to be
recompiled?
Nelson Minar wrote:
> >>As soon as my application grow and more classes are created, I'm
> >>beginning to fee
On Fri, 30 Jul 1999, Ugo Cei wrote:
> Kontorotsui wrote:
> > 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.
Actually jikes sho
> "AC" == Kontorotsui <[EMAIL PROTECTED]> writes:
AC> Hello, so far I worked using the good old xemacs + Makefile
AC> combo. As soon as my application grow and more classes are
AC> created, I'm beginning to feel the weight of a full scale
AC> compilation (like 20 seconds now
. 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,
&
Kontorotsui wrote:
> 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.
Simply use jikes (alphaworks.ibm.com), it's 100 times faster th
I have to agree. Use jikes and just recompile everything. I tried lots
of other hacks with makefiles a dep systems but the best way to make
sure it will work is to just recompile with jikes. I compile a project
with around 300 .java files and jikes rips through tham in a couple of
seconds.
I hop
Michael Emmel wrote:
> >
> > 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 tha
Michael Emmel wrote:
>
> >
> > 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
>
> 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
> .cla
>>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.
>We use make to great advantage. Our system has ~1000 java files and
>mak
[EMAIL PROTECTED] said:
> Kontorotsui wrote:
> > Now, I don't think there is a way to recompile only the class I changed, like
> > we did in C, is this correct?
[..]
> We use make to great advantage. Our system has ~1000 java files and
> make reduces compile time dramatically. ( We use jikes, to
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
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,
24 matches
Mail list logo
