----- Original Message -----
From: "Peter Donald" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 07, 2001 3:28 PM
Subject: Re: Proposed dirlayout document
> At 03:03 7/5/01 +0100, Vincent Massol wrote:
> >1) There is no directory defined for configuration files (top level
> >properties file, top level xml files, manifest file to include in jar,
...).
> >Do we want to define a location for these ?
>
> yup. I recomend
>
> src/conf for config files (as many are manipulated via value substitution)
+1
> src/manifest for manifests .. mainly as it is less unixy than src/etc ;)
>
hum ... do we want so many different directories for config files. I would
prefer just one like src/conf and then leave it up to the project for
creating as many subdirectories as deemed necessary ... Why make it a
special case for manifests ?
> >2) The rule for the output directory says : either bin/ or build/. I
think
> >that a) we must make up our minds on one choice only and b) then names
are
> >not well choosen as they be misinterpreted. I would suggest something
less
> >equivocal like out/
>
> +1 for out (basically intermediates directory right?)
right
>
> >3) Until we all agree, I would let the project decide on how to use Ant :
> >a) as an application that need to be installed on the computer doing the
> >build. This means no need to have ant.jar, optional.jar, xerces.jar,
> >xalan.jar, stylebook.jar, .... in the build/lib directory and no .bat or
.sh
> >files needed either.
> >b) as a "component", i.e. located in build/lib with all it's needed jar
> >files
>
> Again - a lot of projects use build as intermediate directory and it would
> be unnacceptable to have it transmogify into something that contains
> scripts/tools/etc - hence I recomend "tools" dir to hold this if present.
>
No, I meant strategies on how to use Ant : as an installed application vs an
"embedded" application/component.
> >4) The section on docs/ is not clear. Is it output docs not in CVS or non
> >generated docs in CVS. It seems to be both. Should be clarified I think
>
> the problem is the answer is "it depends" until someone implements a
> jakarta wide building of website docs ;)
>
> >5) There should be only one name for the build scripts and tools. I would
> >tend to prefer build/ with the output directory named out/. I don't
really
> >care about the name but there should be only one proposed
>
> I prefer build.xml and build.[sh|bat] if present to be at base of tree
> while the rest of tools/scripts in "tools" dir. This doesnm't cause any
> conflicts with any projects I have noticed.
>
I see. You want to remove the build configuration from the build/tools
directory so that you can have only tools in that directory (basically Ant +
dependent jars) and name it "tools/", right ? So for those who use Ant as an
installed application, this "tools/" directory won't be need (unless they
use other tools).
> >6) 2 options should be left to the project for the external jar needed to
> >build/run the project. Until we reach an agreement on course ... (maybe
> >CJAN/JJAR - see the discussion on jakarta-commons mailing list - will
help)
> >:
> >a) leave the external jars out of CVS. i.e. use a build.properties file
> >(used by Ant) that defines the location of needed external jars
> >b) or check the needed external libs in CVS with the project.
>
> or both ;)
>
Yes. That's why I said "2 options should be left [...]" ... :)
> Cheers,
>
> Pete
Cheers,
Vincent.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
