Antoine
Thank you for the quick response. I wasn't sure whether I'm on the right
track or not. So your response gives me a better sense of assurance.
Yes, as for my local .build.properties, it's not checked in under version
control and holds all the passwords. Is there anyway to encrypt the
passwords for Ant? How's everyone else doing this?
Thanks
----Original Message Follows----
From: Antoine Levy-Lambert <[EMAIL PROTECTED]>
Reply-To: "Ant Users List" <user@ant.apache.org>
To: Ant Users List <user@ant.apache.org>
Subject: Re: Proper Property File
Date: Mon, 22 May 2006 20:01:37 -0400
MIME-Version: 1.0
Received: from mail.apache.org ([209.237.227.199]) by
bay0-mc10-f6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 22
May 2006 17:02:46 -0700
Received: (qmail 95037 invoked by uid 500); 23 May 2006 00:02:45 -0000
Received: (qmail 95026 invoked by uid 99); 23 May 2006 00:02:45 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by
apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 May 2006 17:02:45 -0700
Received: pass (asf.osuosl.org: domain of [EMAIL PROTECTED] designates
213.165.64.20 as permitted sender)
Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by
apache.org (qpsmtpd/0.29) with SMTP; Mon, 22 May 2006 17:02:44 -0700
Received: (qmail invoked by alias); 23 May 2006 00:02:22 -0000
Received: from 207-237-199-120.c3-0.nyr-ubr2.nyr.ny.cable.rcn.com (EHLO
[192.168.11.3]) [207.237.199.120] by mail.gmx.net (mp010) with SMTP; 23 May
2006 02:02:22 +0200
X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo=
Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:[EMAIL PROTECTED]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
X-ASF-Spam-Status: No, hits=-0.0 required=10.0tests=SPF_PASS
X-Spam-Check-By: apache.org
X-Authenticated: #22961642
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
References: <[EMAIL PROTECTED]>
X-Enigmail-Version: 0.94.0.0
X-Y-GMX-Trusted: 0
X-Virus-Checked: Checked by ClamAV on apache.org
Return-Path: [EMAIL PROTECTED]
X-OriginalArrivalTime: 23 May 2006 00:02:46.0439 (UTC)
FILETIME=[38C65370:01C67DFC]
Hello Res,
I think that you are doing the right thing. More exactly, I am not sure
that *the* best practice in this domain exist. As long as you have a
clear policy and you can explain it to all the stakeholders in
your development community, things are OK.
You mention ssh passwords. I have always thought that passwords for
automated scripts are a problem. Either you have these in a file which
is not under version-control, but then you can lose it and
the build is not reproducible. Or the file is just sitting on the
file system at a location where only trusted person(s) can access it,
and it is fine for security, but not for the sake of being sure that the
build
can be setup elsewhere without difficulties. Sometimes, I think it is
quite "funny" when a script user has to "key in" passwords for 10s of
different systems (database servers, application servers, ssh, LDAP,
mainframe connectivity,
...) But it is like that.
Regards,
Antoine
Res Pons wrote:
> Is there any style documentation or suggestion from anyone as to when
> to include properties in the build file and when to put them inside
> the property file, especially when different development teams and me
> the build engineer have to access the same file an do builds?
>
> I set an order of precedence in all development teams build files to
> look for .build.properties first on the user's local drive/home, then
> look for build.propeties in the build subfolder and then in
> build.properties.username last.
>
> In my .build.properties, I use such things as the final build/release
> paths, passwords for the ssh/scp tasks, etc.
>
> Is there a rule of thumb for placement and declaration of properties
> as to whether they should be at the command line upon execution,
> inside the build file or inside one the property files?
>
> Thanks.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
