Return-Path: Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 77551 invoked from network); 12 Aug 2003 12:55:59 -0000 Received: from galen.earthdome.org (206.152.117.245) by daedalus.apache.org with SMTP; 12 Aug 2003 12:55:59 -0000 Received: from mail.more.net (gkar.earthdome.org [192.168.1.1]) by galen.earthdome.org (Postfix) with ESMTP id D162F13108 for ; Tue, 12 Aug 2003 07:55:58 -0500 (CDT) Message-ID: <3F38E3DD.1060500@mail.more.net> Date: Tue, 12 Aug 2003 07:55:57 -0500 From: Glenn Nielsen Organization: MOREnet User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2.1) Gecko/20030224 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: [docs] Crappy build system References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Henri Yandell wrote: > > Actually got to wonder if there's any point having build.properties.sample > in this case. I'm not sure if the rest of build.properties does anything > and these values could sit in build.properties itself [or in the > build.xml]. > > Generally the build.properties file is not in CVS, it is the local version which someone uses to configure where their resources are at. build.properties.sample is committed to CVS and provides a template of what external resources are needed and a default location for them. Regards, Glenn