I'm kinda in the middle of this whole process too and this is what I'm
leaning toward
MyProject
|- source(doesn't get deployed)
|- documentation (doesn't get deployed)
|- static (webserver stuff)
|- styles
|- javascript
|- images
|
To: Struts Users Mailing List
Subject: RE: What's a well defined Struts Project Structure?
I also follow a similar structure in the project, but I have to say that we
have made a mess of it while determining the package structure that now we
have 100s of files in a single folder.
Ideall
TECTED]
Sent: Monday, September 08, 2003 10:36 PM
To: 'Struts Users Mailing List'
Subject: RE: What's a well defined Struts Project Structure?
Here's what I do - based on Erik Hatcher's recommendations in his "Java
Development with Ant" book:
MyProject
| - lib
t: Monday, September 08, 2003 12:06 PM
To: 'Struts Users Mailing List'
Subject: RE: What's a well defined Struts Project Structure?
How about documentation folder and jsp files, where would you put them?
BTW, I was studying a tool called Maven on Apache. I think it's more
rele
ere we can just follow?
-Original Message-
From: Matt Raible [mailto:[EMAIL PROTECTED]
Sent: September 8, 2003 11:06 AM
To: 'Struts Users Mailing List'
Subject: RE: What's a well defined Struts Project Structure?
Here's what I do - based on Erik Hatcher's recom
Here's what I do - based on Erik Hatcher's recommendations in his "Java
Development with Ant" book:
MyProject
| - lib (third party jars, etc.)
| src (.java files)
| test (junit, cactus, webtest tests)
| web
| images
| styles
| scripts
| WEB-INF
| clas
6 matches
Mail list logo