Interesting! Can you show examples of your Ant code using this feature? I
wonder if we should use this in the hackyCore_Build Ant code?
Cheers,
Philip
--On Thursday, March 9, 2006 1:15 AM -1000 Aaron Kagawa
<[EMAIL PROTECTED]> wrote:
At 09:17 AM 2/28/2006, Philip wrote:
Eclipse warnings about Sensors:
Is there any way how to get rid of those pesky "taskdf class
org.hackystat.sensor.*
cannot be found" warnings in Eclipse without installing the
sensors? Those are probably
especially irritating to my developers who have no clue what
Hackystat is. My current
thought would be to make a separate Ant build file that contains
the Ant sensor targets
and invoke that separately. Any other ideas?
That one sounds best to me.
It turns out that what I proposed does _not_ work. Eclipse seems to know
that it is an Ant Build file, thus those warnings still appear. So...
I found this http://ant.apache.org/manual/CoreTasks/typedef.html . A
taskdef is a specialized typedef and in typedef you can set the onerror
attribute to ignore. In my case, this is good because I can ignore the
warnings. And because I use a conditional to run the sensors, ignoring
the failed taskdef doesn't matter.
Using this practice will make it a little harder for me to ensure that
the taskdefs are defined correctly. However, I'll live with that, because
I don't want my developers to keep on seeing those warnings.
Yay.. Finally those warnings will disappear!
Thanks, Aaron
