In Maven, I would turn this into three projects: common, domain, web. The first two would each build a jar and place it into the local repository, and the last would build a war and use those jars. In addition, I would use the standard Maven directory structure for each project.
But you can change the default directory locations for things:
Note that other plugins might also need or assume these locations so there might be other things you have to change also. That is why I stick to the default locations. [ July 24, 2008: Message edited by: Peter Johnson ]
You can customize the directory structure in a Maven project, but it's no fun.
I'm not a big fan of how they laid things out myself, but at least it's standardized. So if someone dumps a (non-customized) Maven project on me, I know where to find the project's components.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.