From ant-dev-return-12574-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org Mon Apr 09 02:11:06 2001 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 27080 invoked by uid 500); 9 Apr 2001 02:11:06 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 27071 invoked from network); 9 Apr 2001 02:11:05 -0000 Message-Id: <5.0.0.25.0.20010408215100.00a82130@mail.earthlink.net> X-Sender: arielpartners@mail.earthlink.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sun, 08 Apr 2001 22:17:07 -0400 To: ant-dev@jakarta.apache.org From: Ariel Partners LLC Subject: Re: "Depend" task for XML? Cc: partners@arielpartners.com In-Reply-To: <3.0.6.32.20010408130846.010f7640@mail.alphalink.com.au> References: <5.0.0.25.0.20010407220550.00a77038@mail.earthlink.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hello: At 01:08 PM 4/8/2001 +1000, you wrote: >Hi, > >Sounds like a fantasic addition ! One question though ... > >At 10:21 7/04/01 -0400, Ariel Partners LLC wrote: > >- other XML files accessed within the XSL stylesheet(s) via the document() > >function. > >How do you plan on doing this? Considering that document() can be dynamic >interpreted? Will you only check it during actual transform ? Hmmmm. Hearkening back to my days as a "make" maven, I would define generic suffix rules that were as smart as possible at figuring out dependencies, but each specific production would also explicitly list dependencies that could not be derived algorithmically. I imagine that a robust XML dependency checking solution would include both a cleverly designed "Depend" type task as well as some new conventional ways for explicitly identifying dependencies. One way to do this would be to have the XMLDepend task accept these (explicit) dependencies as parameters, perhaps as included filesets a la MatchingTask. > >especially the possible new validate and rpm tasks... > >hmmm .. I think we (I) forgot to add RPM task .. will do it as soon as I >get back if no one else does it first ;) kewl. Does that mean the validate task was already added? I am referring to the task that validates an XML file against its DTD, submitted on 3/23 by Raphael Pierquin. Of course, the validation task would also benefit from XMLDepend.... Thanks again, --Craeg >Cheers, > >Pete > >*-----------------------------------------------------* >| "Faced with the choice between changing one's mind, | >| and proving that there is no need to do so - almost | >| everyone gets busy on the proof." | >| - John Kenneth Galbraith | >*-----------------------------------------------------*