> Yep, I expect that the XPathObjectNavigator needs a good deal of work before > we can use it.
I think so too. Could we just borrow Bamboo code and modify it for our needs? Both projects are under GNU licence... Still - it will be nice to ask them if they do not mind. Anyway - write it from scratch shoudn't be very hard (just reflection stuff) but needs extensive testing. Better use what is already done [and well done!] :-) > See this message for my ideas of what needs to be done. > http://sourceforge.net/mailarchive/forum.php?thread_id=3707522&forum_id=32775 > Plus I'm sure there are many bugs that needs to be fixed and unit test that > need to be written. > > I'm hoping to spend a day or two next week getting things into shape, and > hopefully after that creating a new sf.net project for it. > > Any help would be greatly appreciated :) I'll gladly help you. Try use mine patches I sent before - they are good ground to start playing with Bamboo. Write me (privatelly or here) when you look into that - we could cooperate on this field. Martin > ----- Original Message ----- > From: "Martin Aliger" <[EMAIL PROTECTED]> > To: "Ian MacLean" <[EMAIL PROTECTED]>; "Matthew Mastracci" > <[EMAIL PROTECTED]> > Cc: "Scott Hernandez" <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Thursday, January 08, 2004 6:41 AM > Subject: Re: [nant-dev] Re: Inter-Task XML Communication (WAS: new xml type) > > > > Hi all, > > > > I successfully include XPathObjectNavigator from Bamboo.Prevalence. > > > > Script like this: > > > > <exec program="foo.exe" commandline="1 2 3" failonerror="false"> > > <result taskoutput="/ExecTask/ResultCode" property="resultcode"/> > > </exec> > > <echo message="${resultcode}"/> > > > > now correctly writes: > > [exec] foo.exe 1 2 3 > > E:\src\extern\nant\test2\test.build(21,3): External Program Failed: > foo.exe > > (return code was 2) > > [echo] 2 > > > > What is not so nice is: > > > > 1/ Bamboo makes object names from hierarichy based on their names. In NAnt > > we use custom attributes to customize names > > 2/ We could want to hide some names from result (or all public is ok?) > > 3/ Badly formed xpath do not throws exception but rather returns string > > "NAnt.Core.Tasks.ExecTask". > > 4/ Collections returned via xpath (e.g. "/ExecTask/Environment") returns > as > > "NAnt.Core.Types.OptionCollection". Not very useful... > > > > Maybe, I'm doing something wrong with Bamboo... > > > > Attached are patched to NAnt sources + zip with needed Bamboo.Prevalence > > sources. > > Sources are alot simlyfied now (e.g. only one result element) and no fail > > checks yet. It is meant just to test this approach. > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Perforce Software. > Perforce is the Fast Software Configuration Management System offering > advanced branching capabilities and atomic changes on 50+ platforms. > Free Eval! http://www.perforce.com/perforce/loadprog.html > _______________________________________________ > nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers > ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
