timtebeek commented on pull request #113: URL: https://github.com/apache/maven-enforcer/pull/113#issuecomment-939496268
OK the test failure is quite puzzling to me. Not sure I fully grasp what `maven-enforcer-extension` and the `run-its` profile within that are doing, and why it's not working. It appears to 1. launch a Mock Repository Manager, 2. use that for the `maven-invoker-plugin` to try to build `src/it/projects/defaults/pom.xml`, 3. but in doing so fails to resolve the `enforcer:enforcer-api:3.0.1-SNAPSHOT`, 4. which as far as I can tell was never pushed to that mock repository. Of course locally the problem goes away when I run `mvn install`, as that stores the plugin `~/.m2/repository`. Could the failures in Ci/CD have something to do with [the recent removal of the cached `~/.m2/repository`](https://github.com/apache/maven-enforcer/commit/f2743cfbb519a65b62c7117de12172ec4892035f#diff-5dbf1a803ecc13ff945a08ed3eb09149a83615e83f15320550af8e3a91976446)? -- 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]
