> -----Original Message----- > From: Christopher Lenz [mailto:[EMAIL PROTECTED]] > Sent: 25 December 2002 12:34 > To: Cactus Developers List > Subject: Re: [PROPOSAL] New directory structure? > > 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.
Sure, +1 > > > |_ 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. > > > 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? > > 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. Yeah, I thought about that one too but I'm not completely happy with it. It sounds not too bad as a directory name but not very good as a functional subsystem name. I like "Cactus Runners" (although it comes from JUnit). They really are integration front ends that act as cactus enablers/activators/runners/etc. Or shall we come up with a nice Cactish name ... :-) humm, let's see ... What about "Spines". We have the core framework which is the bulk of the Cactus and then several Spines which grow out of the core to activate it! I'm writing this email while flying across the world (London-Mumbai) and I don't have an internet connection available for look for other cactish names... That will have to wait but I'm sure we can find some nice terminology revolving around cactus, if you like the idea of course. I kinda like Spines though :-) Ideas? Thanks -Vincent > > -- > Christopher Lenz > /=/ cmlenz at gmx.de > > > -- > To unsubscribe, e-mail: <mailto:cactus-dev- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:cactus-dev- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
