like: javac a.java b.java f.java
not: javac a.java
javac b.java
javac f.java
this seems to be a very unjam-like thing to do.
=o= Yeah, but that's happens when the compiler does dependency-
based builds. Plain old "make" has this problem as well.
=o= As of Java 1.1, there's also the issue of compiles making
extra .class files with auto-generated names for anonymous
inner classes.
=o= An additional complication is that the javac compiler's
dependency-checking will not necessarily detect complicated
interdependent relationships, unless you make sure to compile
the interdependent source files together. Thus I've found
the only reliable way to work is to group the source files in
directory/package structures and run this command:
% javac *.java
And what they produce is always referred to as *.class, so as
to pick up the anonymous inner class files as well.
<_Jym_>