Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Maven & Java multiple version support

Aberta
  • Algo errado?
#4,564 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, typescript, vscode
Domínio
developer-experience, tooling

Direção de pesquisa

Start by reading the Java extension's Maven project configuration and how it applies compiler settings to main and test sources; the issue does not name specific files or tests. Reproduce with the supplied pom properties, comparing the editor's diagnostics with mvn clean install on the command line. Done means the editor accepts the test sources' configured Java version without reporting invalid language features.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

bug

Describe the bug

I am using BobIDE/VSCode and I don't know if this is supported - I have a pom that inherits jboss-parent and I wanted to have the sources and the tests at different JDK versions. This seems to cause problems as it gets confused and states there are errors with the tests sources having e.g. JDK15 language features even though that is valid. Note that mvn clean install on the command line works fine.

A clear and concise description of what the problem is.

To Reproduce

A typical pom e.g.

  <parent>
    <groupId>org.jboss</groupId>
    <artifactId>jboss-parent</artifactId>
    <version>55</version>
  </parent>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <!-- Compile/target Java 11, built with JDK 17+ (required by spotless 3.x). -->
    <javaVersion>11</javaVersion>
    <maven.compiler.source>${javaVersion}</maven.compiler.source>
    <maven.compiler.target>${javaVersion}</maven.compiler.target>
    <maven.compiler.release>11</maven.compiler.release>
    <maven.compiler.testRelease>17</maven.compiler.testRelease>

Is this an architectural limitation of the underlying eclipse code?

Expected behavior
To function as maven does on the command line.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment

  • Operating System: Fedora44
  • JDK version: Various
  • Visual Studio Code version: VSCode 1.126 / BobIDE 2.2.3
  • Java extension version: 1.58.0

Additional Information

Linguagem predominante
TypeScript
Estrelas
2.3k
Forks
549
Merge médio
4d 21h
PRs com merge (30d)
19

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de redhat-developer/vscode-java

Todas as issues de redhat-developer/vscode-java

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.