Article:		Flexible User and Environment Ant Configuration
Subject:		Including per-user properties in source control
Date:		2004-11-03 01:51:58
From:		randomnoun
I've found if you import a file named "ant-properties/${user.name}.properties" instead of "local.properties", you can allow developers to check their properties into source control systems. Useful for having different build properties for different regions as well (development, acceptance, production).

Showing messages 1 through 1 of 1.

• Including per-user properties in source control
  2004-11-03 16:16:24  gjbremer [Reply | View]
  
  
  That's excellent! One fear that I'd have is that a user would build the war and ear files and accidentally use their local settings. A fear unfounded since I use a designated build user on a build machine under cruisecontrol. How do you juggle the different target deployments -- development, acceptance and production?