Hi Vincent, Vincent Massol wrote:
Hi,
As a christmas gift, I'd like to propose a new directory structure to
follow-up on the new web site presentation email I've sent (provided it
is well received on course ;-)).
Here's the new structure I'd like to propose:
jakarta-cactus
|_ anttasks
(only keep in this subproject the Ant tasks that are not related to Cactus. This subproject is expected to disappear over time as
it is expected Ant will provide solutions to perform what we are
doing)
|_ framework
|_ documentation
|_ samples
|_ sample-servlet
|_ sample-jetty
|_ sample-ejb (in the future)
Could drop the "sample-" prefix here.
|_ frontends
|_ eclipse
|_ ant
(contains Cactus related Ant tasks such as StartTask, StopTask,
etc and reusable Ant scriptlets for several containers. See
the other email entitled "Ant subproject packaging" for more
ideas on the artifacts from this subproject)
As you can see, it is not a major change but I feel it is time to start
putting these additional directories: "samples" and "frontends" to
better compartiment stuff.
Do you like this new structure?
+1 Very much. The current folder hierarchy is too flat.
Hmm, "Front End" is indeed not very clear IMHO, but I'm also having a hard time thinking of a better term. The only term I can come up with is "integration" as a directory name, i.e. integration/ant, integration/eclipse. But I don't like that very much either.We really need a good name to describe what I've been calling Front Ends till now. Is Front End a word you like and find expressive enough? Do you have a better alternative?
--
Christopher Lenz
/=/ cmlenz at gmx.de
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
