Two comments:
1) I would prefer not to include external dependencies. After all, they are,
well, external. I understand, though, that not everyone feels the same way
about this.
2) Where would tools go? For example, the form bean generator. I don't think
they should be in struts.jar, so perhaps a 'tools' directory under src?
--
Martin Cooper
Tumbleweed Communications
----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, February 25, 2001 4: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
>
>
