> ----- Original Message ----- > From: <[EMAIL PROTECTED]> > > But really, shouldn't we be able to define this list in the build file as > normal? Doing > > it with includesfile is going to make me have my build.xml, 7 sub-xml > build files, and 21 > > text-files (3 per xml)... I don't think that is a good solution... > > Well, uh, yeah, thats what 'includes' and <include> is for! :) But this > whole time, I think(?), you've been speaking about an external file > defiining the set of files, have you not? > > Or you could use <echo> and write out the includesfile from the build file. > > Erik
With the old tool, I had 7 xml files being read (by the other build tool).. I am trying to switch it over so those are 7 ant sub-build files... But I need 3 sets of files (ignoring the fact that it would still require a mapper) per xml file. Therefore, I would have to create and maintain 21 txt files if the (7) Ant subbuild.xml(s) can't handle it. Does that make more sense? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
