danielnadean opened a new pull request, #11621: URL: https://github.com/apache/seatunnel/pull/11621
## What changed - Exclude `target` build output directories from `ImportClassCheckTest`s repository-wide JavaParser scan. ## Why - The latest fork CI failure on August 1, 2026 came from `seatunnel-ci-tools` on `unit-test (8, windows-latest)`. - `ImportClassCheckTest` walks `..` and parses every `.java` file it finds. - In the full `clean verify` unit-test workflow, earlier modules have already produced generated Java files under `target`, so this test ends up parsing checked-in sources and build outputs together. - That inflates the JavaParser workload and can trigger `GC overhead limit exceeded` in the Surefire fork JVM on hosted Windows JDK 8 runners. ## Impact - Keep the import check focused on checked-in repository sources. - Avoid repeatedly parsing generated build outputs that are not part of the source tree contract. ## Validation - `./mvnw -f seatunnel-ci-tools/pom.xml spotless:apply` - `git diff --check` - Independent maintainer review of the final diff (static review only) -- 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]
