Hi thathan69420, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

Here are some suggestions to understand and fix classpath vs. module‐path issues:

• If you aren’t using Java modules (no module-info.java), remove any module descriptor and stick with the classpath.
• When using Java 9+ modules, you must place modules on the module‐path at compile and runtime. See how to supply the module flag to JDT.LS:
– How to supply module path to JDT.LS when using Java 9 modules?
eclipse-jdtls/eclipse.jdt.ls#538 (comment)
• In VS Code debugging, you may need to explicitly set modulePaths/classPaths in your launch.json. For example:

{
  "modulePaths": ["${workspaceFolder}/modules/*"],
  "classPaths": ["${workspaceFolder}/lib/*"]
}

See “Cannot resolve the modulepaths/classpaths automatically…”
#1249

Other references with low confidence

• Support adding referenced library into module path – adding modular JARs into modulePath vs classpath
redhat-developer/vscode-java#2272
• Unresolved module error in module-info.java – removing modules makes it work again
#1021
• Handle module projects with separate module-info.java for main and test sources
redhat-developer/vscode-java#2116 (comment)

The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!

Module Path Issue #1540

Description

Activity

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions