Extend GET_PROJECT_INFO command with java settings or provide an additional command
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Description
Extend `GET_PROJECT_INFO` command (or provide an additional command) with java settings -- the source/target/release info is already internally available from maven/gradle parsing itself just not exported to LS protocol.
### Use case/motivation
[This code ](https://github.com/apache/netbeans/blob/e1fbbd88dd1fac6b933ae625d9af00b58edac168/java/java.lsp.server/vscode/src/jdk/validation/project.ts#L92) will need to be updated when new command becomes available or existing one extended
### Related issues
_No response_
### Are you willing to submit a pull request?
No
Contributor guide
Research direction
Trace the GET_PROJECT_INFO command in the Java language server and the Maven/Gradle parsing paths that already hold source, target, and release settings. Review java/java.lsp.server/vscode/src/jdk/validation/project.ts to understand the consumer; done means the settings are exposed through the LS protocol, either by extending the command or adding a new one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100