Greetings, all, The autoconfig system is now available for testing. To use it, invoke:
ant -f autoconfig.build.xml This will do two things: - overwrite your current modules.build.xml file with an automatically generated one. - create/overwrite a sample.hackystat.build.properties file in the parent directory that contains a hackystat.build.properties file with all discovered modules. It does this by discovering all the local.build.xml files, parsing them to find the <module>.required.modules and its property, generating the dependency tree, topologically sorting it, and then writing out all of the currently required targets for modules.build.xml. (I think. :-) A couple of caveats: - I haven't written the code to check for an out-of-date modules.build.xml file yet. - As you play with it, you might inadvertantly commit your auto-generated version of modules.build.xml. This isn't necessarily bad, but I've committed a file called orig.modules.build.xml to make it simpler to recover the manually written version. Please play with it and let me know if you discover any problems. After we're confident in it, I'll delete the modules.build.xml file and add the additional code needed to deal with this. Cheers, Philip
