Actually, if you print out the Ant manual, you'll find it is 76 pages long. I hardly consider that spartan. In fact, for an open source project (which are notoriously bad at documentation, for obvious reasons), I think the Ant manual is outstanding, and I offer many kudos to the Ant developers for taking the time to put together such good docs.
As for the Apache FAQ being down, I have to agree with you. I wish the Apache folks would just go back to using the Faq-o-matic until Jyve is stable. Sincerest regards, Chris Todd Software Engineer Alabanza Corporation [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2000 4:23 PM To: [EMAIL PROTECTED] Subject: RE: Some Thoughts on Ant 1.3 and 2.0 spartan doc + no faq = frustrated user (enough said?) -----Original Message----- From: Diane Holt [mailto:[EMAIL PROTECTED] Sent: Friday, October 27, 2000 12:49 PM To: [EMAIL PROTECTED] Subject: RE: Some Thoughts on Ant 1.3 and 2.0 --- Samuel R Listopad II <[EMAIL PROTECTED]> wrote: > I think it would be good to have a property like output set to > '/usr/${currUser}' > and then when using ${output} and currUser set to alice it would resolve > to /usr/alice rather than the > /usr/${currUser} that it is now (if output defined before currUser). Why not just use ${user.name}? It's available at startup. One thing it might be good to do, is to have a list of the "built-in" properties -- maybe in an appendix to the doc. I just modified my ant wrapper script to not pass any defines on the java command-line, then ran ant with -debug on a build-file that has nothing but a <project> tag, piped it to "grep Setting project property:" and captured all the properties that are set without my having anything to do with setting them. One thing I found interesting (and hadn't realized before this) is that basedir is set without my having set it in <project>. Also, it doesn't look like the project name is ever assigned to a property. Another candidate for an appendix would be to pipe the debug to a grep on "+User task:" -- for example, I've never seen anything in the doc about <compileTask> (although I might remember having seen some mail about it once, not sure, need to check the archive). Diane ===== ([EMAIL PROTECTED]) __________________________________________________ Do You Yahoo!? Yahoo! Messenger - Talk while you surf! It's FREE. http://im.yahoo.com/
