Organizing java projects, packages

Question

I'm making an application that has about 50 classes. I am using the project to learn how to do a lot of things, but one is how to use packages. I would like to get your comments on what I've done, since I've never done this before.
I set up a directory called /java/classes/package_name/ for all my .class files.
Likewise, /java/src/package_name/ has the source files.
Now, I'd like to be able to build all the source files and put them into the appropriate class path directory. Is there a standard way of doing this? Do you use make? I like make, but is there a better tool? I like simple things.
I have several classes in my package that have mutual dependencies. I think this is a bad thing, but it's because some of them are input dialogs and such, so I couldn't think of any way to handle buttons and input fields other than to have some mutual dependencies.
I can't compile them at all because they depend on each other (or so I think). Is there a standard way to organize the GUI files like this? Do they not even belong in a package?
If they don't belong in the package, where do they belong?
I also want to be able to package this up nicely in a jar file or something so I can give it to friends to run (it's a game with some 2D graphics). I would have to include the class files in package_name package, but how do i related them to the main class when I jar them up?
There are actually two programs that use all most of the files, and there could be more later.
Thanks very much ahead of time; I appreciate all your info and tips.

Answer 1

I am not opposed to learning to use Eclipse for Java type things,Good, good, good... also download and play with Netbeans, among others... use the one which suits you most... I use several IDE's for different jobs.
but I'd rather learn to do it manually first. Otherwise I will by as mystified as ever when things go wrong.You'll go far. A BIG downside of the modern IDE's automatic build-and-deploy features is they hide all the "plumbing", which is great as long as it works, but leaves the user (esp noobs) totally at a loss when something goes wrong, coz the user doesn't even what should be happening... let alone what's not happening, or why, or what to do about it.
Resolving dependencies like you suggested works fine when you don't have mutual dependencies.AFAIK the Java compiler doesn't have a problem building classes with "mutual dependencies"... for instance if class A uses class B which uses class A the compiler doesn't require a definition of type B (trusting that such will be forthcoming) when it compiles A... it then compiles B... and the picture is complete.
An experiment to dis/prove the above notion
package forums;
public class A {
  public final String message = "A";
  public static void main(String[] args) {
    A a = new A();
    System.out.println(new B(a).message);
class B {
  final String message;
  B (A a) {
    this.message = a.message + "B";
}This works, so I don't get the whole "Resolving dependencies" problem. Do you know something that I don't?
Javac "follows" dependendencies automatically, as long as the files are in the expected place.
Me thinks you're just having classpath issues... you're directory structure must EXACTLY match your package structure... and remember that Java is cAsE sEnSiTiVe, even if the underlying operating system is not... ie: I think the "circular dependencies" problem is a furphy.
Read that classpath article... of you're still stuck give us a yell and we'll work through compiling and running the above program.
Cheers. Keith.