redhat-developer / redhat-developer/vscode-java
maven profile was activated by language server's java version
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.3k
- Forks
- 546
- Avg merge
- 20h 1m
- Merged PRs (30d)
- 11
Description
Extension: redhat.java-1.34.0
Problem: the project runtime is JavaSE-1.8, but the maven profile in "hibernate-validator" jar was activated by language server's minimum requirement java version(17), and the "javafx.base" compiled by jdk11 was imported in "Maven Dependencies".
<profile>
<id>jdk11+</id>
<activation>
<jdk>[11,)</jdk>
</activation>
<dependencies>
<dependency>
<groupId>org.openjfx</groupId>
<artifactId>javafx.base</artifactId>
<version>11.0.0-SNAPSHOT</version>
</dependency>
</dependencies>
</profile>
Expect: profile to be activated by project runtime version
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 reproducing the issue with a JavaSE-1.8 project, the redhat.java-1.34.0 extension, and the hibernate-validator Maven profile shown in the report. Trace how the language server chooses the JDK for Maven profile activation and verify that javafx.base is not imported when the project runtime is Java 8.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript, vscode
- 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