Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 27255 invoked from network); 10 Jul 2000 03:30:23 -0000 Received: from leopard.ardec.com.au (root@203.11.83.9) by locus.apache.org with SMTP; 10 Jul 2000 03:30:23 -0000 Received: from obelinux.adl.ardec.com.au (IDENT:root@obelinux.adl.ardec.com.au [192.168.83.88]) by leopard.ardec.com.au (8.10.1/8.10.1/NC19991210) with ESMTP id e6A3ULT29487; Mon, 10 Jul 2000 13:00:21 +0930 (CST) Received: (from tcook@localhost) by obelinux.adl.ardec.com.au (8.9.3/8.9.3) id MAA07897; Mon, 10 Jul 2000 12:44:42 +0930 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14697.16290.881346.341344@obelinux.adl.ardec.com.au> Date: Mon, 10 Jul 2000 12:44:42 +0930 (CST) From: tcook@lisa.com.au To: ant-dev@jakarta.apache.org, jeff@socialchange.net.au Subject: Dev environment for multiple Ant-based projects In-Reply-To: <3966950F.C59FFDB2@socialchange.net.au> References: <3966950F.C59FFDB2@socialchange.net.au> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Jeff Turner writes: [znip!] We have come to a similar solution, but we don't make it as automated as you do. Each project has a script called environment.sh (or something similar). The developer is then required to set any variables which may not have sensible defaults, and then source environment.sh They can then do as they will. If they want to set up their .bashrc with the correct 'export's and 'source's then that's up to them. Regards Tom