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

   ## CI Fix
   
   The `integration-tests` jobs were failing on JDK 25 and 27 (but not JDK 17) 
because additional IT fixtures use legacy plugin tools that cannot process Java 
17 class files produced by the new default (`maven.compiler.release=17`).
   
   **Root cause:** `sisu-maven-plugin:0.3.5` embeds ASM with Java 11 as the 
maximum supported class version (class major 55). `maven-plugin-plugin:3.6.4` 
also uses internal JDK APIs that break under JDK 25. When the IT harness 
compiles fixtures at the new default Java 17 level (class major 61), these 
tools fail during annotation/descriptor processing.
   
   **Fix:** Added `maven.compiler.release=8` override on install verifiers in 
the remaining affected tests (the same pattern already applied by the previous 
commit for mng-5382, mng-5561, etc.):
   
   - `MavenITmng5530MojoExecutionScopeTest` — plugin (sisu 0.3.5 + 
plexus-metadata 1.5.5), extension (sisu 0.3.5), extension-plugin (sisu 0.3.5)
   - `MavenITmng5578SessionScopeTest` — plugin, extension, extension-plugin 
(all sisu 0.3.5)
   - `MavenITmng5742BuildExtensionClassloaderTest` — plugin (sisu 0.3.5)
   - `MavenITmng7474SessionScopeTest` — plugin (sisu 0.3.5)
   - `MavenITmng7310LifecycleActivatedInSpecifiedModuleTest` — extension (sisu 
0.3.5 + maven-plugin-plugin 3.6.4)
   - `MavenITmng7349RelocationWarningTest` — artifacts (maven-plugin-plugin 
3.6.4)
   - `MavenITmng5640LifecycleParticipantAfterSessionEnd` — extension (sisu 
0.3.5), badplugin (maven-plugin-plugin 3.6.4)
   - `MavenITmng8106OverlappingDirectoryRolesTest` — plugin 
(maven-plugin-plugin 3.2)
   - `MavenITmng11796DefaultPhasesStandardLifecycleTest` — extension-plugin 
(maven-plugin-plugin 3.6.4)


-- 
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