redhat-developer / redhat-developer/vscode-java
Support adding referenced library into module path
Open
Nobody has claimed this yet.
JPMS
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
In a modular project, if the project requires a referenced library from the module-info.java, the project will fail because we are now always adding the referenced libraries into classpath.
Maybe we should try to add them into modulepath if:
- The project is a modular project
- The lib is a modular jar
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where referenced libraries are always added to the classpath, using the project’s module-info.java handling as the entry point. Check how modular JARs are identified and define completion as placing eligible libraries on the module path for modular projects while preserving existing classpath behavior otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100