Nico Seessle <[EMAIL PROTECTED]> wrote: > I see a fourth:
> 4) Add if/unless-attributes to the fail-task. Then you could write your > build.xml in one target > <available property="mylogger" classname="mylogger.Logger" /> > <fail message="Required 'mylogger' not found" unless="mylogger"/> > and one could use this task to validate that properties are set in other > places (for example using -D on the command-line) I agree that this adds flexibility, but requires two task lines to do one thing in my case. Both (unless attribute in fail and require attribute in available) make sense. My remaining question is: Am I allowed to change existing code or should this be requested to the original developers ? Bert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
