> Ian MacLean wrote: > > >> > > yeah - its implemented as an xslt script now - ie it > doesn't execute > > any tasks ( <include> included :) ). Perhaps a better > implementation > > could be written that processes the includes as well. It could > > probably be done with xslt but that may not be the best approach. > > > > Do you want to log a bug for this ? > > > looks like you already did :) > Ian >
Indeed I did. Some thought needs to be given to the whole namespace issue. For example, shouldn't there be a schema for NantContrib, with its own namespace? You might have a build file: --- begin test.build --- <?xml version="1.0" encoding="utf-8"?> <project name="test" default="all" xmlns="http://nant.sf.net/schemas/nant-0.85.win32.net-1.0.xsd";> <echo message="Building test project"/> <property name="path.build" value="${directory::get-current-directory()}"/> <include buildfile="scm.include"/> <target name="all" depends="GetSource" description="build everything"> <!-- other tasks --> </target> </project> --- end test.build --- With an include file: --- begin scm.include --- <?xml version="1.0" encoding="utf-8"?> <project name="scm" default="all" xmlns="http://nant.sf.net/schemas/nant-0.85.win32.net-1.0.xsd"; xmlns:contrib="http://nant.sf.net/schemas/nant-contrib-0.85.win32.net-1.0.xs d"> <echo message="Included file project"/> <target name="GetSource"> <contrib:vssget localpath="${path.build} dbpath="..." project="..." /> </target> </project> --- end scm.include --- ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&op=click _______________________________________________ Nant-users mailing list Nant-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nant-users
