Re: how to access a SQL database through ANT

ant sql just uses jdbc. You'll need the jdbc drivers for your database. If you dont have access to a database already, then yes, you'll have to install the database. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional com

Re: Grep?

gt; > > > > > > > > > tofile="${ant.working.dir}/props.xml" overwrite="true" /> > > semanticattributes="true" keepRoot="false"/> > > > NO double property entries found !! > > >

Re: Grep?

ks of Antelope f.e. , that are (yet ?!) not > merged into antcontrib. > > So i use both > antcontrib 1.0b2 and Antelope 3.2.10 > > Regards, Gilbert > > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greg > Akins > Sent:

Grep?

ure because the file can contain some errors) I'm using to run sql*plus... The results get dumped to ant's logging, and I want to search for particular ora- errors? Any tips that don't involve me writing my own Ant task? Any help

RE: "unless" doesn't appear to work for me?

> > > > > > You might want to look at the task to ckeck whether or not > the file exists. > > -Rob A > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional c

Re: "unless" doesn't appear to work for me?

Quoting Matt Benson <[EMAIL PROTECTED]>: > > This is "the Ant way," ordinarily. > I chose "the Ant way";'). Thanks very much for everyones help! - This mail sent through IMP: http://horde.org/imp/ --

Re: "unless" doesn't appear to work for me?

Quoting Dominique Devienne <[EMAIL PROTECTED]>: > 1) Thinking if="foo" means "execute the target is foo's property value > is true (or yes, or 1)". It sounds like you're are not making that > mistake. > Here is the target I'm running (this is the only target in this buildfile, and fileToCheck &

"unless" doesn't appear to work for me?

I have two targets. One has a "if", the other has an "unless" that both evaluate the same property. I conditionally set the property based on the length of a file. when I echo the property before the target, if it's set, I get "true" If it's not set, I get ${file.exists} (which I assume mean t

Re: Failing a "Successful" build

> if you want the nested failure to propagate, set failonerror="true" in > > > I had thought that I already did this.. But I double checked and had left it out. Thanks very much. - This mail sent through IMP: http://horde.org/imp/ --

Failing a "Successful" build

ure this in a "wrapping" build. Any help is greatly appreciated. Greg Akins Insomnia Consulting www.insomnia-consulting.org - This mail sent through IMP: http://horde.org/imp/