Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Message-ID: <017101c24494$bbb95890$1219570f@ranier>
From: "Steve Loughran" <steve_l@iseran.com>
To: "Ant Users List" <ant-user@jakarta.apache.org>
References: <1029433706.3d5be96ac83b2@mail.spamcop.net>
Subject: Re: nested properties anyone?
Date: Thu, 15 Aug 2002 12:48:28 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


----- Original Message -----
From: <bo@spamcop.net>
To: "Ant Users List" <ant-user@jakarta.apache.org>
Sent: Thursday, August 15, 2002 10:48 AM
Subject: Re: nested properties anyone?


> Quoting Steve Loughran <steve_l@iseran.com>:

> > > 2. What is a work around?
> >
> > -save all your per system settings in a properties file
> > -pick the file name from a property
>

> We have more than 20 possible servers. I think it is much uglier to have
20+ one
> line files than a single file with 20 entries. But thank you for a
suggestion.

Once you have >1 property per server, the separate file approach is pretty
clean.

imagine have a per server file containing:

-options for controlling web.xml items
-flags as to which version of servlet api you use
-name of j2ee server
-information used for an automated deployment (ftp host, user, password,
directory)

This stuff works very well with separate property files, not least because
sensitive deployment systems dont need to have their config kept under SCM,
you just keep it in a well protected file on one or two systems that
operations run, not development.

-steve


--
To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>