Paul, This is an excellent question and one I'm struggling with too. I'm trying to follow a similar convention to SUN's but I know the Maven-ites have another format that I can see has value but not sure where this leaves us with best practices. I wanted to follow /dist /conf etc. I think you can change the project descriptor to get the effect you want but it would be nice to know why MAVEN went with something different from well-defined blueprints etc.
Thanks, Manny -----Original Message----- From: Paul Faulstich [mailto:[EMAIL PROTECTED] Sent: Monday, August 01, 2005 10:52 AM To: [email protected] Subject: Maven Recommended Directory Structure I've been browsing through the archives looking for some documentation regarding the thought process that went into the Maven directory structure conventions, but haven't found much yet. We are restructuring one of our projects, and it would be helpful to be able to explain to others (and to understand myself) why Maven's recommendation differs from Sun's (http://java.sun.com/blueprints/code/projectconventions.html#92194). In particular: - directory names (target vs dist, resources vs conf) - the purpose of the /main folder under src (src/main/java vs src/java) - placing tests under src (src/test vs test/testname/src) If this is a dead horse, then please just point me to the discussions that already exist. Thanks, Paul -- Paul Faulstich Systems Analyst L.L. Bean, Inc. Freeport, ME 04033 (207) 552-2294 [EMAIL PROTECTED] www.llbean.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
