+3/4..
with the exception of the docs directory. Instead of separating by type of
document, I think the docs should be separated by content. Like the user
guide should go in "docs/userGuide", the bean developer guides possibly in
"docs/developerGuide/struts-bean.xml" or
"docs/tags/struts-bean.xml".
-----Original Message-----
From: Craig R. McClanahan
To: [EMAIL PROTECTED]
Sent: 2/25/01 7:10 PM
Subject: [PROPOSAL] Struts Source Directory Structure
Based on the proposal to include unit tests in Struts, there is a desire
to revise the organization of the source repository. Here is a summary
of my understanding of the most recent proposal, plus some enhancements
to be complete, with annotations on the contents of each directory.
jakarta-struts/
build/ Build scripts and batch files
conf/ Config files for components
share/ Config files for struts.jar
unit/ Config files for unit tests
doc/ Source documentation files
xdocs/ XML input docs and stylesheets
lib/ JAR files of dependent packages
(if we agree to include any)
src/ Java sources for components
example/ Sources for example webapp
share/ Sources for struts.jar
test/ Sources for test webapp
unit/ Sources for unit tests
upload/ Sources for upload webapp
target/ Output of "build" processes
-- no files in CVS repository
dist/ "build dist" output (i.e. the
current nightly distribution)
sdk/ "build sdk" output (i.e. the
proposed Struts Dev. Kit)
unit/ Output of unit test runs
web/ Webapp sources for components
blank/ Web files for blank webapp
example/ Web files for example webapp
template/ Web files for template webapp
test/ Web files for test webapp
upload/ Web files for upload webapp
Comments?
Craig
