Changes since 24.4.12
Fixes
-
Exclude project maven dependencies from isolated class loader (#20523)
Commit · Pull requestIf the user project directly or transitively depends on maven artifacts, mojos can fail at runtime because of Maven API loaded from both isolated class loader and maven.api realm. This change prevents maven artifacts from being added to the isolated class loader.
-
Fix class and resource loading in maven plugin (#20465)
Commit · Pull request · Issues 19616, 19009, 20385Run Flow mojos using an isolated class loader that includes both project and plugin dependencies, with project dependencies taking precedence. This ensures that classes are always loaded from the same class loader at runtime, preventing errors where a class might be loaded by the plugin's class loader while one of its parent classes is only available in the project’s class loader (see #19616). Additionally, this approach prevents the retrieval of resources from plugin dependencies when the same artifact is defined within the project (see #19009). This refactoring also introduces caching for ClassFinder instances per execution phase, allowing multiple goals configured for the same phase to reuse the same ClassFinder. It also removes the need to instantiate a ClassFinder solely for Hilla class checks, reducing the number of scans performed during the build.
-
Move blocking calls outside session lock (#19938) (#20475)
Commit · Pull requestMove blocking calls outside session lock (#19938)
-
Fix ServletFileUpload header encoding (#20480)
Commit · Pull request · Issue