[MCOMPILER-469] compiler plugin uses arkane rules to decide what the source code level is

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Assignee: Robert Scholte
• Reporter: Henning Schmiedehausen
• Created: 22/Jun/21 23:13
• Updated: 30/Aug/23 16:22
• Resolved: 11/Sep/21 09:34

Description

When compiling a java 8+ code base, unless there is an actual <source>8</source> configuration parameter to the plugin, the plugin will ignore other directives such as <parameter> because it believes that the compiler is a 1.7 or older compiler.

e.g.

<plugin>
  <artifactId>maven-compiler-plugin</artifactId>
  <version>3.8.1</version>
  <configuration>
    <release>11</release>
    <parameters>true</parameters>
  </configuration>
 </plugin>

will silently ignore the <parameters> flag as it believes the compiler to be ancient.

This should be better documented or it should also consider checking the <release> setting to determine what version the compiler is. 

As a workaround, we set the <source> and <release> configuration to the same value.

 

 

Issue Links

• duplicates: MCOMPILER-413 Parameters does not work when only release is specified