RE: conditions in antlib?

2010-11-12 Thread Ludwig, Michael
> have you given something like > > > > > > > > a try? What do you get?? I haven't tried that. I have yet to explore . I was thinking of something like this: But I don't know if you can adapt it to your purposes. Michael

Re: conditions in antlib?

2010-11-12 Thread Stefan Bodewig
On 2010-11-12, Stefan Bodewig wrote: > On 2010-11-12, wolfgang haefelinger wrote: >> I want to provide a *single antlib* with the following requirements: >> (a) must work with Ant 1.7.x and newer >> (b) uses appearing to be a 1.8.x feature. > I'm sorry but I don't know of any way to do that.

Re: conditions in antlib?

2010-11-12 Thread Stefan Bodewig
On 2010-11-12, wolfgang haefelinger wrote: > I want to provide a *single antlib* with the following requirements: > (a) must work with Ant 1.7.x and newer > (b) uses appearing to be a 1.8.x feature. I'm sorry but I don't know of any way to do that. > In other words, don't we need a conditional

Re: conditions in antlib?

2010-11-12 Thread wolfgang haefelinger
Sorry, for hitting the wrong button! Michael, have you given something like a try? What do you get?? This is what I get: tryme.xml:4: The following error occurred while executing this line: Invalid task in antlib condition class org.apache.tools.ant.TaskAdapter does not extend o

Re: conditions in antlib?

2010-11-12 Thread wolfgang haefelinger
Hello Michael, have you given something like On Fri, Nov 12, 2010 at 2:04 PM, Ludwig, Michael wrote: > Moin Wolfgang, > >> I want to provide a *single antlib* with the following requirements: >> (a) must work with Ant 1.7.x and newer >> (b) uses  appearing to be a 1.8.x feature. > >> do

RE: conditions in antlib?

2010-11-12 Thread Ludwig, Michael
Moin Wolfgang, > I want to provide a *single antlib* with the following requirements: > (a) must work with Ant 1.7.x and newer > (b) uses appearing to be a 1.8.x feature. > don't we need a conditional component-, type-, > macrodef and taskdef definition?? You could parse ${ant.version}. ant.

Re: Conditions

2005-03-22 Thread Antoine Levy-Lambert
If you do not use ant-contrib, you have to have 2 targets when something is dependent upon a condition > So I'm trying to execute the mail task based on a conditional statement. > I'm not sure if I'm doing this incorrectly or not. Basically, what I > want out of this target

RE: Conditions

2005-03-22 Thread Bill Rich
To avoid the procedural logic you could have done the following: This is more within the philosophy/architecture of Ant. Bill -Original Message- From: Rich Harris [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 22, 2005 11:10 AM To: Ant Users List Subject: RE: Conditions

RE: Conditions

2005-03-22 Thread Rich Harris
-Rich -Original Message- From: David Resnick [mailto:[EMAIL PROTECTED] Sent: Monday, March 21, 2005 9:37 PM To: 'Ant Users List' Subject: RE: Conditions The only action a condition task performs is set a property if the condition is true. You can then use the property you have s

RE: Conditions

2005-03-21 Thread David Resnick
The only action a condition task performs is set a property if the condition is true. You can then use the property you have set/not set to be the condition for a separate target (using the if or unless attribute of the target). If you want an if statement, you can find a task that works as one in