http://robwilkerson.org/2008/09/15/ant-build-templates-why-two-files/feed 2008-10-21T23:42:45-04:00 Chyrp tag:robwilkerson.org,2008-10-21:/id/108//comment_2112 2008-10-21T23:42:45-04:00 2008-10-21T23:42:45-04:00 Rob Wilkerson http://robwilkerson.org <p>@jim – </p> <p>Yeah, for my needs 1 is sufficient if it’s organized decently. Any more than that just feels cumbersome. If I had more “sections”, I might break them down into separate files, but I find one just works better for me and is easier to keep up with.</p> tag:robwilkerson.org,2008-10-16:/id/108//comment_1899 2008-10-16T22:58:50-04:00 2008-10-16T22:58:50-04:00 Jim Priest http://www.thecrumb.com <p>I’ve got several property files and have been thinking of condensing them down…</p> <p>build.properties – generic stuff related to project<br /> ${server}.properties – info related to each server we deploy to<br /> ${user}.properties – info specific to my local machine<br /> auth.properties – username/passwords</p> <p>But I’ve also seen single property files that are difficult to wade through. </p> tag:robwilkerson.org,2008-09-17:/id/108//comment_251 2008-09-17T07:53:49-04:00 2008-09-17T07:53:49-04:00 Rob Wilkerson http://robwilkerson.org <p>The perfect analogy. Thanks, Julian. Having a separate properties file is useful when I’m running my own builds, but it’s been <em>invaluable</em> when running the builds of other developers where I’m less familiar with the details project and its code. The separate build file very precisely specifies what I need to change before the build can be run successfully. I never have to touch the build script itself.</p> tag:robwilkerson.org,2008-09-16:/id/108//comment_237 2008-09-16T14:50:15-04:00 2008-09-16T14:50:15-04:00 Julian Simpson http://www.build-doctor.com <p>Right on. I think of it like string literals in code; your build.properties file is really runtime configuration for your build. It tends to lead to flexible builds as you can drop in a new config file. Nice post!</p>