hi

I'm planning a project structure for new projects and I'd be interested in getting feedback on what other people feel is a good project structure, preferably one that has has endured the test of time.

I'm planning on using Ant for builds and packaging. Eclipse could be used as the official development IDE but I'd like to leave the door open so that developers can use the environment they like best (Emacs, JDeveloper etc.).

I've been reading the Sun Java Blueprints Guidelines article Project Conventions for Enterprise Applications (http://java.sun.com/blueprints/code/projectconventions.html) on the subject. Does anyone have practical experience in using these conventions?

The project structure for the Petstore sample application would look something like this when following the conventions:



petstore/
apps/
opc/ # order processing center component
build/
opc-ejb/
build/
src/
conf/
java/
com/
sun/
j2ee/
blueprints/
opc/
...
test/
build.xml
opc-war/
build/
src/
conf/
java/
...
test/
web/
WEB-INF/
jspf/
lib/
tags/
tlds/
web.xml
html/
jsp/
build.xml
src/
conf/
build.xml
supplier/ # supplier component
...
build/
components/
comp1/
build/
src/
conf/
java/
...
test/
build.xml
dist/
docs/
lib/
setup/
test/
build.properties.sample
build.xml
LICENSE.txt
README.txt



br. aspa