Return-Path: <amooy@home.nl>
Mailing-List: contact turbine-maven-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list turbine-maven-user@jakarta.apache.org
Received: (qmail 12461 invoked by uid 98); 11 Dec 2002 23:18:59 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Received: (qmail 12442 invoked from network); 11 Dec 2002 23:18:57 -0000
Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142)
  by nagoya.betaversion.org with SMTP; 11 Dec 2002 23:18:57 -0000
Received: (qmail 97688 invoked by uid 500); 11 Dec 2002 23:17:41 -0000
Received: (qmail 97670 invoked from network); 11 Dec 2002 23:17:40 -0000
Received: from mail7.home.nl (HELO mail7-sh.home.nl) (213.51.128.24)
  by daedalus.apache.org with SMTP; 11 Dec 2002 23:17:40 -0000
Received: from Sauron ([217.120.167.27]) by mail7-sh.home.nl
          (InterMail vM.5.01.05.09 201-253-122-126-109-20020611) with ESMTP
          id <20021211231746.KYMI2885.mail7-sh.home.nl@Sauron>
          for <turbine-maven-user@jakarta.apache.org>;
          Thu, 12 Dec 2002 00:17:46 +0100
From: "Age Mooy" <amooy@home.nl>
To: "'Turbine Maven Users List'" <turbine-maven-user@jakarta.apache.org>
Subject: RE: Newbie question: Current best practice for web apps
Date: Thu, 12 Dec 2002 00:18:24 +0100
Message-ID: <00d901c2a16b$9a8a9060$0201a8c0@groni1.gr.nl.home.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
In-Reply-To: <0C072E7CC947D511AC9600A0CC734120885D95@XEON400>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N


I'll summarize what I've said before on the turbine-dev list:

My src tree looks like this:

/src
  /java
  /schema (used by the Torque plugin)
  /test
  /webapp
    /logs
    /resources
    /templates
    /WEB-INF
      /conf
      /web.xml

If you run the war:webapp goal with this kind of src dir structure it
will generate a complete webapp directory structure under
${maven.build.dir}/${pom.id} for you, including the classes compiled
from src/java, the dependent lib files, and everything that exists under
src/webapp.
The war:war goal generates exactly the same thing but then inside a war
file.

You can point tomcat at ${maven.build.dir}/${pom.id} in its server.xml
file and run your webapp from there.

The only (tiny) problem is that now you have to run war:webapp to deploy
any changes, even for changed templates, images, etc. I use the maven
console so running war:webapp takes about 1 second.

I use maven 1.0 b7.

If anyone is interested I can xdoc this and send it to the list.

Age


> -----Original Message-----
> From: Lester Ward [mailto:lward@tagaudit.com] 
> Sent: Wednesday, December 11, 2002 23:13
> To: 'turbine-maven-user@jakarta.apache.org'
> Subject: Newbie question: Current best practice for web apps
> 
> 
> In the mail archive, there seems to have been some lively 
> discussion about what the proper way to handle web 
> applications is. It appears that at one time, files for web 
> applications (e.g. WEB-INF, etc.) were kept in the 
> "webapps/<appname>" directory, but this was later changed to 
> just be a single "webapp" directory per project. 
> Unfortunately, neither of these schemes is mentioned in the 
> project layout recommendation page 
> (http://jakarta.apache.org/turbine/maven/reference/dirlayout.h
tml), so it's unclear what I should do.

Can someone please summarize the current thinking on how Maven should be
used when building a web application?

Thanks.

--
To unsubscribe, e-mail:
<mailto:turbine-maven-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail:
<mailto:turbine-maven-user-help@jakarta.apache.org>