> one. For now, the ugly method is the most portable:- > > <!DOCTYPE project [ > <!ENTITY IncludeBuildCore SYSTEM "buildCore.xml"> > <!ENTITY IncludeBuildSecondary SYSTEM "buildSecondary.xml"> > ]> > > <target name="includedBuild"> > &IncludeBuildCore; > &IncludeBuildSecondary; > </target>
Thanks, we already do use this method and it sucks. We need to pull some global shared config snippets from the tools repository, but there is no easy way to determin location before the parser runs with out providing our own wrapper Ant class, or native scripts which we are trying to avoid. > The cleaner method using XInclude/Xpath will let you include named targets > from one build file or another, using the xpointer syntax. You'll need to > wait for the W3C proposals to finalise and the java XML parsers to implement > it before using xpointer references. Um... ok, os there is a solution so I have to wait for it... so it isn't a solution; next. > <large-antcall-snip/> We also already make use of antcall and some patched versions of antcall which make up som deficencies with the original. This does not help when including config at all. > Looks like there is no app level xml include. That is too bad... =[ I think when I get to the next round of build system mods I will move the config to script tasks then use jython to drive the config, using ant for the building parts which it is very good at, but a pain to config. --jason ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
