Table of contents
Common Caused by: Causes of exceptions
jar package is missing
jar package conflict
Common Caused by: Causes of exceptions
ClassNotFoundException belongs to checkException and usually appears when the project starts. The reasons for this problem are summarized as:
jar package is missing
Not correctly imported jar results.
jar package loss solution
Check whether the jar package in the workspace is downloaded correctly (if it exists, see if the version is correct)
jar package conflict (most difficult to detect)
Multiple versions of jars are referenced in the project, resulting in version conflicts. Due to version upgrades, the methods used may have been abandoned.
jar package conflict resolution
Check whether the workspace references multiple versions, if appropriate, remove them