Maven & Java multiple version support #4564

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