Detect and prevent newly-added imports #8
Description
Javadocs also respect imports, and sometimes IDEs like to automatically add imports when referencing external classes. This poses a problem when a javadoc comment written in the workspace references a class via a newly-added import, because that import does not get saved, and the reference will error upon a fresh setup.
This problem is difficult to detect during review, because you'd need to have a workspace open to see all the imports. So, we need to find a solution to detect these newly-added imports, and fail a verification check if it finds them.
Preliminary thoughts: We'll need to persist the import info somehow; two possible ways are saving list of imports to a file and comparing, or comparing between the workspace version and the source from the sources JAR.