I don't think I ever did this myself but I recall reading this question in
the old Java FAQ. I'm certain that the answer said you had to compile them
both at the same time. I think the command line needs to look like this; I'm
not certain this is 100% right but it should be pretty close:

   javac my\com\foo.java my\othercom\bar.java

I also seem to recall that if the source files are in the same directory,
you can do a:

   javac *.java

and all source files in the directory will get compiled. Again, I'm not
certain of the exact syntax but I think it is pretty close to what I have
given.

--
Rhino

Hello,

You are able to tell javac where to find you source files using the
-sourcepath flag. From the docs (
http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/javac.html ):

"-sourcepath sourcepath Specify the source code path to search for
class or interface definitions. As with the user class path, source
path entries are separated by colons (:) and can be directories, JAR
archives, or ZIP archives. If packages are used, the local path name
within the directory or archive must reflect the package name.

   Note that classes found through the classpath are subject to
automatic recompilation if their sources are found."

I hope that helps,
Carl.

The package names of your classes need to match the directory structure.
 Also you need to be in a directory above the top of your package
directory to compile the files.  So if you have a class:

/com/knutejohnson/programs/MyProgram.java

and a class:

/com/knutejohnson/components/MyComponent.java

you need to be in the / directory and enter:

javac com/knutejohnson/programs/MyProgram.java

This will compile both files and then you can run the program with:

java com.knutejohnson.programs.MyProgram

This is one of the most difficult subjects to explain and understand
when you first start using packages.  It is only exceeded by CLASSPATH.
 Using jar files with packages is done similarly.

Have you considered using a build tool like apache ant? If  you're going
to be doing a lot of this then the extra effort to define the build
configuration will be worth the pay off.