Development directory Structure [closed]

Answer 1

Although we don't use Maven, we use the Maven directory structure.

We've found that it accurately reflects the concepts we need (e.g. separation of deployment code from test code, code from data, installers from code). Also we figure that if someday we switched to Maven, most of our process would remain the same.

Answer 2

After a couple years working with different structures I recently found a structure that hols most variations for me:

/project_name     (everything goes here)
  /web            (htdocs)
    /img
    /css
  /app            (usually some framework or sensitive code)
  /lib            (externa libs)
    /vendor_1
    /vendor_2
  /tmp
    /cache
  /sql            (sql scripts usually with maybe diagrams)
  /scripts
  /doc            (usually an empty directory)

Answer 3

A 2011 update: http://java.sun.com/blueprints/code/projectconventions.html

Answer 4

I just found a interesting document about Directory structures on Zend website:
http://framework.zend.com/wiki/display/ZFDEV/Choosing+Your+Application%27s+Directory+Layout