- From: Dimitris Dimitriadis <dimitris@ontologicon.com>
- Date: Fri, 7 Dec 2001 22:21:22 +0100
- To: "Arnold, Curt" <Curt.Arnold@hyprotech.com>
- Cc: "'www-dom-ts@w3.org'" <www-dom-ts@w3.org>
OK; could/should we use the attributes for the "external" tasks and keep your design for the "internal" ones? I'm trying to safeguard against major revisions if Ant were to go the attribute way. /Dimitris On Friday, December 7, 2001, at 09:50 PM, Arnold, Curt wrote: >> 1. Point to patch files as if they were in a separate >> directory, it's a >> cosmetic but irritating point that they are the only ones floating >> around in the top-level directory > > That the patch files are needed at all is also irritating, I'll move > them. > > >> 2. Could we kame use of the descritpion attribute on the >> top-level tasks >> instead of creting out own usage targets? ant -projecthelp lists them >> and you get relevant statement directly from the tasks (got >> this tip in >> an email about the Ant/xalan problems we've had) > > The description attribute is helpful, unfortunately there are a lot of > targets that are not intended for external use (they'd make good > "private" > tasks if there were such a concept) and the resulting output of > projecthelp > won't distinguish between the useful targets and the not so useful ones. > > I've also done some piecemeal changes to eliminate the <get>'ing of > static > content (the specs, jsunit, junit) when they are available locally. > I'll > finish that up and they will make running the build while offline > painless. > --- Dimitris Dimitriadis dimitris@ontologicon.com http://www.ontologicon.com
Received on Friday, 7 December 2001 16:23:48 UTC