Description
When hunting down some "Used undeclared dependencies" warnings, I found the plugin lying. For example, the line
java.lang.Object var = bean.field;
does not impose a direct dependency on the field's type, whatever it may be. Likewise, the line
bean.method(null);
does not directly depend on the method's return type nor parameter types. Unless I explicitly code a reference to a type by means of variable declarations, type checks/casts etc., there is no need to declare dependencies that are already brought in via transitivity, that's what Maven was invented for, isn't is