Re: build.xml

[Grant Smith]

Just a side-question to the svn:externals thing: If I make a change to the main build.xml file. Is the only way to see it propagated to the subprojects by doing a svn commit; svn update in the subprojects ? I'm doing a lot of experimentation, and I dont want a bunch of commit messages while I do so. I also dont want to have to copy my changes to the subproject build directories if there's an easier way ? Thanks, Grant. Grant Smith wrote: Thanks for the info, folks. Yes, trust me, I won't leave build.xml in this state :) My current thinking as to why *.tld is not expanded in non-win32 environments is due to us using <arg value="...">. I'm now experimenting with <arg path="..."> instead which is supposed to be more OS-friendly. Sean Schofield wrote: If you've been making subproject-specific changes and committing them, please roll those back ;-) sean On 7/11/05, Bruno Aranda <[EMAIL PROTECTED]> wrote: Yes, there is only one build folder, which is svn:externalized (or whatever is the word here), so every subproject has the same build structure. What make every subproject build different is a set of properties situated in the parent folder of every subproject (a build.properties file). As there is only one build file, it cannot contain any subproject adaptation and has to be the same for every subproject. Only some tuning in the build.properties files is valid ;-)... Bruno 2005/7/11, Grant Smith <[EMAIL PROTECTED]>: I need some help understanding how the current build systems works. Are all the individual build.xml files actually svn_externals of the main build.xml file ? That would explain why I can't make modifications to each one, and commit them. Any insight would be greatly appreciated. Thanks, Grant . .