+1 to Alex's comments. Having to create your own build.properties is a bad idea because, in addition to being an extra setup step, when the template for it changes you won't know and you won't pick up the intended changes.
A standard build.properties should exist and work if you use a standard setup. People using a nonstandard setup should override with local.properties. - Gordon -----Original Message----- From: Alex Harui [mailto:aha...@adobe.com] Sent: Monday, April 15, 2013 11:04 PM To: dev@flex.apache.org Subject: Re: Git and build.properties I just pulled and tried ant release and it immediately failed because there is no build.properties. I liked the old way we had it which was: 1) a build.properties is in version control 2) anything you need to override in your system was changed in local.properties for which there was a local.template.properties It had the advantage of not requiring a file to be copied to just run the default build configuration. The build.xml still references local.properties. What are the advantages of the build.template.properties way of doing things? Can we go back to local.properties? Won't it be easier to have a default build.properties that works on the CI server and the release kit builds instead and have all overrides in local.properties (and env.properties)? Thanks, -Alex On 4/14/13 6:40 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > Hi, > >>> The local changes can be made in this file. The template remains >>> unchanged. >>> >>> We can add a specific entry into gitignore for the build.properties file. >> >> I'll give it a try and see if I can get it to work. > > Looks like I got it working, checked in - as always feedback welcome. > > Thanks, > Justin -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
