[Anthill] Question on keeping build.properties when building

[Edward Zarecor]

My workaround is to check the build.properties files for all of my
environments into source control, appending the environment to the end
of the filename:

build.properties.integration
build.properties.development

from anthill I specify which file to use in the switches to ant

-propertyfile build.properties.integration.

Seems a little cleaner to me, your mileage may vary.

Ed.

On Mon, 2004-12-06 at 10:24, Eric Minick wrote:
> Hi Magnus,
> 
> I think a work around like the one you're describing would be the way to 
> do it for now. There really isn't anything that preserves the working 
> directory (or some part of it) in the current release.
> 
> Regards,
> 
> Eric
> 
> Magnus.Mickelsson at hm.com wrote:
> 
> >Hi,
> >I just started up with Anthill OS 1.7.1 after trying out CruiseControl (gack!).
> >
> >My question is: How can I make sure that files in the work dir (files not in CVS, like build.properties) are not deleted every build? Is there a possibility to add an exclude pattern or something? I am in a Windoze environment.
> >
> >I tried setting a write protection on the files, but alas! no success.
> >
> >Of course I could do a workaround by copying the files from somewhere in a pre-script to the real one, but it's kind of ugly IMHO.
> >
> >Thanks in advance,
> >Magnus
> >
> >_________________________________
> >Magnus Mickelsson
> >H & M Hennes & Mauritz AB
> >Direct phone: +46 8 796 14 93
> >Cell phone: +46 704 922182
> >mailto:magnus.mickelsson at hm.com
> >
> >_______________________________________________
> >Anthill mailing list
> >Anthill at lists.urbancode.com
> >http://lists.urbancode.com/mailman/listinfo/anthill
> >
> >
> >  
> >
> 
> _______________________________________________
> Anthill mailing list
> Anthill at lists.urbancode.com
> http://lists.urbancode.com/mailman/listinfo/anthill
-- 
Edward Zarecor <edward_zarecor at harvard.edu>
Harvard University