----- Original Message -----
From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 17, 2001 12:19 AM
Subject: Re: [DISCUSSION] conf/MANIFEST.MF -> src/conf/MANIFEST.MF ?
>
>
> On Mon, 16 Apr 2001, Geir Magnusson Jr. wrote:
>
> > Scott Sanders wrote:
> > >
> > > Geir Magnusson Jr. wrote:
> > >
> > > > Any reason why not? It's src, of sorts.
> > > >
> > > > One less directory at the top level.
> > > >
> > > > geir
> > >
> > > Fine with me. Go for it. I just copied from collection, IIRC.
> >
> > I know - I did the same thing yesterday setting something else up. Just
> > seems neater. Waiting for Peter or Craig to set us straight :)
> >
>
> I *think* I get to blame this one on Vincent :-). It was his suggestion
> that configuration files go in "conf" rather than "src/conf".
>
arghhhh .... too late to join the fun ... I hate these time lags .. :)
Yes, Craig, it was my proposition to put in <component root>/conf.
For me everything under <component root> is source (that's why it is under
CVS for me) and the src/ directory are the java sources *and* configuration
files that are located at the same level as the java packages. However, I
would put in <component root>/conf configuration files that should be
visible by the end user and that they could modify + all misc. configuration
files.
For the substitution, it happens in all directories : src/, conf/ docs/,
build/ (oopss sorry you don't want a build directory right ?:) ), web/, ...
Have a look at the Cactus conf/ directory and tell me where I should put
this stuff. If you put conf under src/conf, then you'll want to put web/
under src/web and then why not docs/ under src/docs also, .... ? So in the
end you'll end up with :
<component root>
|_ src/
|_ some build.xml files and other misc.
> > geir
> >
> > --
> > Geir Magnusson Jr. [EMAIL PROTECTED]
> > Developing for the web? See http://jakarta.apache.org/velocity/
> >
>
> Craig
>
Vincent
