gnodet commented on PR #13922:
URL: https://github.com/apache/maven/pull/13922#issuecomment-6774622601

   <!-- forgebot -->
   
   Diagnosed and fixed the CI failures.
   
   **Root cause**: The PR raises `maven.compiler.release` to `17` via system 
property in the IT helper. Because system properties override POM properties, 
five IT fixture plugin builds that relied on old build tooling started 
receiving Java 17 class files they cannot parse:
   
   | Test | Plugin | Error |
   |---|---|---|
   | `MavenITmng5382Jsr330Plugin` | `maven-plugin-plugin:3.2` | 
`ArrayIndexOutOfBoundsException: Index 2387 out of bounds` |
   | `MavenITmng6084Jsr250PluginTest` | `maven-plugin-plugin:3.2` | 
`ArrayIndexOutOfBoundsException: Index 2387 out of bounds` |
   | `MavenITmng5561PluginRelocationLosesConfigurationTest` | 
`maven-plugin-plugin:3.6.0` | `Unsupported class file major version 61` |
   | `MavenITmng6972AllowAccessToGraphPackageTest` | 
`plexus-component-metadata:1.5.5` | `ArrayIndexOutOfBoundsException: Index 4162 
out of bounds` |
   | `MavenITmng7836AlternativePomSyntaxTest` | `sisu-maven-plugin:0.3.5` | 
incomplete Sisu index → HoconModelParser not registered → 
`MissingProjectException` |
   
   **Fix**: For each test, explicitly set `maven.compiler.release=8` on the 
verifier that builds the legacy plugin/extension, overriding the global default 
for that specific invocation. The fixture is purposely compiled at Java 8 since 
the test verifies DI injection behaviour, not Java version compatibility.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to