Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Maven & Java multiple version support

Abierto
  • ¿Algo no está bien?
#4,564 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java, typescript, vscode
Área
developer-experience, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
TypeScript
Estrellas
2.3k
Forks
549
Merge medio
4 d 21 h
PR fusionados (30 d)
19

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de redhat-developer/vscode-java

Todos los issues de redhat-developer/vscode-java

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.