I'm a bit confused by this but interested... If a developer has to maintain a configure.xml for his environment that generates a build.properties via this task, then what's the difference to the developer maintaining a build.properties directly?
Mind you on a philosophical point, developers should follow the standard FS layout of the project ;-) > -----Original Message----- > From: Martin Gee [mailto:[EMAIL PROTECTED] > Sent: 30 April 2001 05:49 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: [SUBMIT] Configure task (much like UNIX configure tool) > > > Hi Gents, > > FROM OUR DOCS.... > > A good build environment needs to be easily portable from machine to > machine. Developers are picky about laying out directories > their own way. > This configure task was inspired by the linux configure > command. Where, > before doing a source tree build we need to inspect a users > evironment for > the third-party libs needed to complete a build. > Externalizing the transient > pieces of your build enviroment help mitigate diverse user > environments. > This task will bootstrap your development environment by creating > aproperties file that contains transient items such as > compiler settings and > classpaths. This task uses the inherient search capabilites > of patterns and > filesets. See ANT docs for description(s) of patternset and fileset. > > > Attached files: > ************************************************** > > org.apache.tools.ant.taskdefs.optional.ConfigurTask.java > org.apache.tools.ant.taskdefs.optional.PathProperty.java > > configure.xml (example) > configure.html (Docs) > ************************************************** > > Cheers, > Martin Gee >
