Heya Ian, > >Would anyone be interested in a patch for that behaviour? Or is it > >undesirable (as it seemed to be for Gary at least)? > > > > > Definately.
I take it that definitely was directed at the "interested in a patch". ;) > I vaguely started looking at it a while ago but didn't get > much done. The current implementation uses an xslt stylesheet to process > the buildfile and generate the projecthelp output. Xslt probably isn't > really the right tool for this ( hey I was doing a lot of work with xslt > at the time and when you've got a hammer everything looks like a nail ) > however some kind of custom parsing will likely be necessary - rather > than using NAnt's project class to load the includes. XSLT may still be useful - we can use it to identify all of the targets _and_ the include nodes. The target nodes we just print out the name attribute and the include nodes we open up the specified buildfile and recursively repeat. I agree that using NAnt's project class wouldn't be the best way forward. > Feel free to ping me or the list with any questions about the > implementation. Thanks Ian. If I find some time in the coming weeks I'll give it a shot. I'll be sure to ping you (and probably the dev list) if I get stuck. :) However, right now I'm more focussed on writing custom tasks and possibly working on the solution task (the lack of custom build tasks is a showstopper for me using that task) so this might have to take a back seat for awhile. Cheers, Matt ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Nant-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nant-users
