slachiewicz opened a new pull request, #1762: URL: https://github.com/apache/maven-dependency-plugin/pull/1762
Part of #1759. #1760 kept 22 ITs in a serial execution because they deleted or asserted on fixture artifacts that other ITs resolved from the shared `target/local-repo`. Each of those ITs now has fixtures of its own: - the five `get-*` ITs use `<it>-dep` and `<it>-dep-transitive` instead of the shared `get-artifact` pair, which stays for the two ITs that only depend on it; - the five purge ITs on the `purge-local-repository` pair use `<it>-dep` and `<it>-dep-2`; - `purge-local-repository-snapshots-only` uses `purged-snapshots-only`, and `purge-local-repository-multi-module-execution` uses `purged-exec-a` and `purged-exec-b`. The remaining six serial ITs already used fixtures no other IT touched. With no sharing left, the `integration-test-shared-repo` execution goes and every IT runs in the parallel one. `purge-local-repository-multi-module` checked for files named `purged-a` and `purged-b` at the repository root, which never exist; it now checks the purged jars. Verified: `mvn -P run-its verify -Dinvoker.rerunFailingTestsCount=0` on macOS (8 cores, JDK 17) → 114 ITs pass in 64, 83 and 82 s over three runs; the purge ITs only delete their own fixtures, plus `maven-model:sources:2.0.9`, which only `purge-local-repository-bad-dep` uses. -- 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]
