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 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914500#3914500 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914500 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
