Filter diagnostics based on classpath/imports

[kathrynkodama]

Possibly can use the JavaModelUtil.getClasspathEntry method

[kathrynkodama]

Possible design decision around if we should show diagnostics if the API is not on the classpath, but it is clear they are intending to use that API given the import statements. We should compare to LSP4MP and JDT LS

In the below screenshot, we should not deliver the diagnostic on HelloServlet as the WebServlet import is incorect.

[bensonnw]

• Validate JakartaEE annotations
• @Generated annotation is missing support for method parameters
• Add a warning if Java class annotated by @WebServlet annotation has unknown super type
• Check all interfaces for Java class annotated by @WebFilter annotation
• Check interface hierarchy for Java class annotated by @WebListener
• Filter BeanValidation diagnostics based on classpath/imports #297
• Filter Persistence diagnostics based on classpath/imports #298
• Filter JAXRS diagnostics based on classpath/imports #299
• Filter JSON diagnostics based on classpath/imports #300
• Filter ManagedBean diagnostics based on classpath/imports #301
• Filter DependencyInjection diagnostics based on classpath/imports #302
• Filter WebSocket diagnostics based on classpath/imports #303

[kathrynkodama]

#159 looks related to Check interface hierarchy for Java class annotated by @WebListener also see the issues tagged project-info-needed Cannot be implemented until there is logic to get more information from the Java project

[bensonnw]

Closing it as all PRs are merged