redhat-developer / redhat-developer/vscode-java
Compiler options in pom.xml are not obeyed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
VSCode with the RedHat Language Support for Java extension does not obey javac compiler options specified in the Maven pom.xml when compiling projects.
Environment
- Operating System: Debian 12
- JDK version: 21.0.1
- Visual Studio Code version: 1.87.0
- Java extension version: 1.29.2024030608
Steps To Reproduce
- Compile the sample project via
mvn compile. Note that no errors or warnings are produced. - Open the sample project in VSCode and wait for the Java extension to build it. Note that 1 warning is produced.
Sample project:
https://github.com/paulmedynski/vscode-java-compiler-args
Current Result
VSCode produces compiler errors and warnings that are disabled in pom.xml.
Expected Result
VSCode compiles the project with the same compiler options specified in pom.xml.
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 with the linked sample project and compare mvn compile with the VSCode Java extension build, using the pom.xml compiler options as the expected behavior. Trace how the extension imports or applies those options, then verify that VSCode produces the same diagnostics as Maven.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100