Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Goal: macrodef a task based on exec, and make timeout optional in the defined task just as it is in the underlying exec task.
If I don’t provide a default for <attribute name="timeout"/>, then ant requires a timeout.
If I provide a default of "", then the exec task complains.
Do I really need to create a conditional that asks if the timeout parameter has a value other than a silly default, and then have two copies of the exec invocation depending?
I don’t see a clean way to do it without a conditional. But if you’re not too fussy, you could go with a really long default value of timeout – e.g. a day or a week or a year’s worth of milliseconds.