Source Code Structure

Question

I know there are a ton of different ways to structure your code. Been searching around the this forum and other google farming results and so far this is what I have come up with. If you have a better solution or dislike the way I do something I would love to hear about it. We have a new project and wanted to get started off on the right foot so we are pretty open to most things.
/apps
  /myapp
    /lib
      (where are my jars go ofcourse)
    /src
      /com/mycompany/myapp
        /domain
          (all the objects that represent my domain)
        /repository
          (all my DAOs)
        /service
          (all the stuff that manipulates my domain options)
        /web     
          (all my controllers...perhaps other web specific things too)
    /test
      (all my tests that directly correspond to the above package structure...ie if I want to test a domain object it would be located at /test/com/mycompany/myapp/domain/MyObjectTest.java)
    /web
      (static file such as images, scripts and such)As you can see it is for a web application but similar principles could apply for other applications as well (minus the web stuff).

Answer 1

You're mixing two concerns here:
1.) How to structure your project directory with source/tests/libraries and
2.) How to structure your packages.
I'll ignore concern number 2 for now, as it's a pretty separate question.
Personally, I've come to like the way Maven wants its projects to be set up by default. That setup makes sense, even if you don't use Maven:
/myProject
  /src
    /main
      /java
        (this directory contains all production Java code)
      /resources
        (this directory contains all non-Java code resources that are needed for production)
      /web
        (this optional directory contains web-related resources, JSPs, WEB-INF, ...)
    /test
      /java
        (this directory contains all test Java code, JUnit tests, ...)
      /resources
          (this directory contains all non-Java code resources that are needed for the tests)
  /target
    (this directory is not checked into version control and is where all artifacts are built into. It's the only directory that gets modified during a build, leaving all other areas to be modified by the developer only)Note that there is no /lib directory, since Maven makes it unnecessary for the libraries to be contained in the project directory.If you don't use Maven, then I suppose you could just add a /lib directory at the top level.