I'm very new to Ant, but it seems like the <mapper> task combined with something else might be what you're looking for. Can someone else that has experience with <mapper> chime in?
________________________________ From: nagish <[email protected]> To: [email protected] Sent: Wednesday, May 13, 2009 2:51:11 PM Subject: Re: Merge base settings with environment specific ones Yes, merging or concatenating two files together is non-issue if you explicitly tell the Ant script what files to merge. But remember the Ant build script is expected to be used for building anything that follows the same convention. What this means is that the Ant script can not hardcode the setting file names in it as they are unknown at the time of writing the Ant script. As I said earlier, the thing that I'm not sure how to do with Ant is that once the Ant script gets a set of base setting files, i.e. those that don't have environment tag embedded in their names, how it can iterate through the set to pair each base file with the corresponding environment specific one, i.e. "a.properties" with "a.dev.properties", "b.properties" with "b.dev.properties", ... etc, so that each pair of files can be merged together to form a new setting file to be packaged into the application that is being built... Eric Fetzer wrote: > > Since they don't contain the same settings couldn't you just append one > file to the end of the other or something similar with <concat> maybe? > -- View this message in context: http://www.nabble.com/Merge-base-settings-with-environment-specific-ones-tp23524997p23529636.html Sent from the Ant - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
