Hi everyone,
it seems that the <if> task has regressed, throwing an exception when
only 'unless' condition is defined on it. It's simple to workaround
(just use test="${not (unlessCondition)}" instead ), but annoying none
the less. What's more, the task parsing exception thrown does not
contain any line/location information (it's cut off after "at :"). Is
this a known issue?
Kind regards,
Leszek 'skolima' Ciesielski
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
nant-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nant-developers
