Question

Java class files inside jars can be easily replaced and modified. For instance, the following command can be used to replace a compiled class file within a jar:

jar uf JarFile.jar com\something\Class.class

If the class file was replaced with a file such that no dependencies were broken, then the code is still able to execute. The same happens with class files that are not inside jars.

Is there any way to validate a set of class files (whether inside a jar or not) to see if all their dependencies are present and not broken?

I do not want to prevent class files from being modified but rather to be able to verify that changes are valid (with respect to dependencies). The compiler does this check (dependency-check) at compile time, but once the classes are compiled, how can one verify the class files themselves?

Answer 1

Just loading the class will ensure that.