Aslak Hellesřy - 2001-04-11

Logged In: YES
user_id=49846

I have identified and fixed the bug. It happens if you're
using iControl. If only a subset of the project is to be
instrumented, then dependency checking should only be done
on the classes/sources in question. The old dependency
checking mechanism considered that reinstrumentation was
necessary if ANY class file was older or missing.

iContract won't generate classes for missing classes, but
the task's dependency logic would assume that.

I'll test and upload the new source over easter.

Catching the exception is not possible as long as the
iContract task executes forked (in a different VM). I think
the forked execution is necessary because of classloader
issues, but i don't remember 100%. I'll look at it.