I've used Maven2 to manage my newest project, and I'm quite happy with all the freebies you get when you follow their standard directory structure: builds, source builds, unit testing, test coverage, site building, dependency management (inside eclipse, too) etc. The site-building module for Maven2 still feels beta-quality, but that's about my only complaint.
So basically I'm saying "me too" to Igor's post below :-) On 9/22/06, soir <[EMAIL PROTECTED]> wrote:
My multimodule project's directory structure looks like (it's suggested by Maven): workspace\projectname workspace\projectname\src\main\java workspace\projectname\src\main\resources workspace\projectname\src\main\webapp workspace\projectname\src\main\webapp\images workspace\projectname\src\main\webapp\script workspace\projectname\src\main\webapp\style workspace\projectname\src\main\webapp\META-INF workspace\projectname\src\main\webapp\WEB-INF workspace\projectname\src\test\java workspace\projectname\src\test\resources workspace\projectname\target\classes Daniel Jue wrote: > > Hi, > > I'm relatively new to Tap, and I am starting with Tap 4 and Eclipse. > I've been using the directory structures as seen in Kent Tong's book. > I also noticed the Tapestry examples (vlib and workbench) have html > files that live in the root of the application, instead of in web-inf. > Is this a standard thing to do? > > I've read that things inside web-inf can't be accessed directly by a > web browser, so that seems like the correct place for the .page/.jwc's > to go. > > Like I said, I have something that _works_, I am just curious to see > if there are benefits to other methods, or drawbacks to mine (i'm sure > my approach is naive): > > workspace\projectname > workspace\projectname\build\classes (output dir for compiled classes) > workspace\projectname\deploy (holds my war file when I export from > eclipse) > workspace\projectname\src\mypackage\ (no .java at this level) > workspace\projectname\src\mypackage\model\ (classes that know nothing > about tapestry) > workspace\projectname\src\mypackage\controller\ (classes for pages and > components) > > workspace\projectname\src\META-INF\ (holds hivemind.xml and sessions.xml ) > > workspace\projectname\WebContent\css (css files) > workspace\projectname\images (jpgs) > workspace\projectname\META-INF (I think eclipse made this dir and > manifest.mf for me) > > workspace\projectname\WEB-INF (all my .html, .page and .jwc files live > directly in WEB-INF, as well as projectname.application and web.xml) > workspace\projectname\lib (hold jars for jscookmenu, BIRT, etc) > > workspace\projectname\reporting\BIRT (holds birt engine, jars, resources, > etc) > > > When I export my project to a WAR, things in > workspace\projectname\build\classes > get put in > WEB-INF\classes > > Please let me know what you think. I'm sure you guys have better > organized project structures. For instance, do your Tapestry projects > look like this? > http://java.sun.com/blueprints/code/projectconventions.html > > Daniel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/What-does-your-project-directory-structure-look-like--tf2315087.html#a6441834 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
