redhat-developer / redhat-developer/vscode-java
When projects are built from maven tab, compilation results are not reflected in JAVA problems tab
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
My project is composed by the following:
- java, maven, spring boot
- one main directory with several maven modules
Currently my settings are:
"maven.executable.options": "-am",
"java.configuration.updateBuildConfiguration": "automatic",
"java.import.maven.enabled": true,
"java.dependency.packagePresentation": "hierarchical",
"java.dependency.syncWithFolderExplorer": true,
"java.autobuild.enabled": false,
"java.debug.settings.onBuildFailureProceed": true,
Since i disabled the java autobuild (following a suggestion from #4100 ), i build my project using maven (using the maven tab)
When i build, i can see i can see the maven build logs in the terminal tab, but that outcome is not reflected in the problems tab.
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
Reproduce the issue from the Maven tab with the listed settings, especially java.autobuild.enabled set to false, and compare the Maven terminal output with the Problems tab. Trace the Maven build entry point and the diagnostic reporting path. Done means compilation failures from the Maven build are reflected in the Problems tab for the multi-module project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- 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