On Friday, August 17, 2001, at 01:27 am, Jeff Turner wrote:
>>
>> Anyways a pseudo convention of using "target/" as intermediate directory
>> has
>> occured in commons/struts projects. Because this doesn't cause any
>> conflicts
>> and thus could be integrated into all apache projects (ignoring egos) I
>> say
>> we move towards it. The easier it is to build projects the more likely
>> we are
>> to see developers work with Apache.
>
> What does "target" mean, or imply?
>
> I can understand "build" ("the results of the build process") and "bin"
> (binaries, ie non-source, implying build output), but "target" is a bit
> vague to me.. is it where results from all build "targets" go? No..
>
> Enough of the world uses build/ for me to be comfortable with it. My vote:
> 0
>
> --Jeff
I too, would advocate "build". "bin/**" intuitively looks like it might
be binary tools or libraries rather than build output, "target"
intuitively sounds like it might contain target specific build information
- e.g. build code to build variants for different platforms. If there's a
need for something different to allow a consistent move for all, then
something like "building" might be worth a thought, it implies a build in
progress, another thought would be to put all build output into a "tmp" or
"temp" directory giving something like "tmp/build/org/.." and
"tmp/dist/....jar". This makes it plain that removal of the "tmp"
directory does not remove anything that cannot be reproduced from source.
Stuart.
-------------------------------------------------------------------------
Stuart Roebuck [EMAIL PROTECTED]
Lead Developer Java, XML, MacOS X, XP, etc.
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
