>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.
[newly proposed directory structure skipped]
>Comments?
I see the benefit of the test webapp and certainly won't want to skip
on that.
However I don't think 'unit' to be an intuitive name for testing the
struts framework itself. I'd therefor rather have the testing framework
under 'test' and rename the current test to something like 'try' or
even 'tryout' (agreed, not exactly good names either but possibly
closer to what this webapp is intended for).
Possibly my reluctance to use test for anything other than actually
testing the framework does come from the naming convention of (almost)
all GNU projects. I'm simply rather used to that convention :)
To add my comments to another thread as well:
I'm strongly in favor of leaving 'dependency files' out of the struts
developer edition. And I do favor this for the very same reason Craig
mentioned - it forces developers to consider interoperability as a
virtue in itself.
As many others mentioned the 'user edition' should be made to run out
of the box with a little hazzle as possible.
Best,
Michael
--
Vote against SPAM - see http://www.politik-digital.de/spam/
Michael Gerdau email: [EMAIL PROTECTED]
Do still life on your computer--run Windows.
PGP-keys available on request or at public keyserver
