Don't analyse things that are surrounded by catch (ClassNotFound)

[pettermahlen]

If a code block has:

try {
  foo();
} catch (ClassNotFoundException e) {
}

then there is no point in analyzing foo(); because it may be an optional dependency

Similarly, we could try to do more advanced analysis by keeping track of infected variables and method calls.
Something is infected if it is mutated or invoked within a ClassNotFound-try block.
Furthermore, something is also infected if it's reading a variable that is infected.

Example:

static {
  try {
    Class.forName("Bar");
    hasClass = true; // infected
  } catch (ClassNotFoundException e) {
    hasClass = false;
  }
}

// ...
void foo() {
  if (hasClass) { // infected
   Bar.bar();
  }
}

We could also try to find references to Class.forName(CONSTANT_STRING) and mark all such classes as infected.

[pettermahlen]

We should probably analyse the benefits of this before doing too much implementation - this feels like something that can be quite complex to build, so we should try to understand if it's going to give value before building it.