Return-Path: 
 <struts-user-return-14084-apmail-jakarta-struts-user-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-struts-user-archive@jakarta.apache.org
Received: (qmail 72609 invoked by uid 500); 26 Jul 2001 09:12:11 -0000
Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: struts-user@jakarta.apache.org
list-help: <mailto:struts-user-help@jakarta.apache.org>
list-unsubscribe: <mailto:struts-user-unsubscribe@jakarta.apache.org>
list-post: <mailto:struts-user@jakarta.apache.org>
Delivered-To: mailing list struts-user@jakarta.apache.org
Received: (qmail 72602 invoked from network); 26 Jul 2001 09:12:11 -0000
Received: from portal.uk.saic.com (HELO saicuunet.uk.saic.com) (194.131.227.2)
  by h31.sny.collab.net with SMTP; 26 Jul 2001 09:12:11 -0000
Received: from [172.24.16.13] by saicuunet.uk.saic.com
          via smtpd (for h31.sny.collab.net [64.208.42.41]) with SMTP;
 26 Jul 2001 09:12:20 UT
Received: by uk-gat-exs01.ds-s.com with Internet Mail Service (5.5.2650.21)
	id <LT0GFJC9>; Thu, 26 Jul 2001 10:11:19 +0100
Message-ID: <7F4F675CE892D3119FD200508B61B21401E4FC60@uk-gat-exs01.ds-s.com>
From: "Prior, Simon" <Simon.Prior@ds-s.com>
To: struts-user@jakarta.apache.org
Subject: Project startup advice
Date: Thu, 26 Jul 2001 10:11:16 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N

Hi Guys,

I am starting a new project and am going to use struts as the framework and
ant as the build tool.  The project is going to be fairly large (having
several subprojects) and as such I need to have a well structured
development heirarchy for development of EJB's, JSP's etc.  I would like
some advice on how best to partition the source files, project
documentation, jar files, dtd's, tld's etc.  Currently I see the project
being War'd up and deployed by ant automatically and wondered what the best
way to write the build script was, maybe each subproject having its own
build.xml and a recursive call to them?

My question at a basic level is, when starting a new project, how do you
structure your development directory heirarchy to aid clarity and ease of
build (any automation ideas would be most appreciated).

Thanks in advance,

Simon.
For optimum solutions that save you time, visit www.ds-s.com.