On Fri, 17 Aug 2001 13:51, Lavandowska wrote:
> --- Peter Donald <[EMAIL PROTECTED]> wrote:
> > I just noted that target is used as intermediate directory name. As
> > this
> > doesn't conflict with any existing "standards" - what do you think of
> > making
> > that the standard for jakarta. I can approach avalon/james/ant people
> > to
> > change it to target ... thoughts?
>
> Though I have no binding vote, I prefer "build" over "target". After,
> all "build" is what you are doing.
True but you are building to a particular "target" ;) It doesn't have to make
sense.
> If we want to standardize (and I do think that is a good idea), I
> suggest that a "poll" be taken of all the Jakarta projects, and the
> naming convention most widely used be adopted by the rest. This seems
> to be the "democratic" means (as each project/subproject casts one
> "vote").
The problem is that many of the projects that adopted the layout of turbine
use build to contain build scripts, tools used during build process and
property files used while building. IIRC in these projects you usually go
something like
cd <base>/build
./build-turbine.sh
While build is the most "popular" intermediate destination at jakarta (and
outside) this would be unnaceptable to these projects. The reason is that it
would cause pain every CVS update because build is a directory in CVS and a
temporary directory locally. This would cause error messages to spout each
update.
--
Cheers,
Pete
*-----------------------------------------------------*
* "Faced with the choice between changing one's mind, *
* and proving that there is no need to do so - almost *
* everyone gets busy on the proof." *
* - John Kenneth Galbraith *
*-----------------------------------------------------*
