slachiewicz commented on issue #186:
URL: https://github.com/apache/maven-verifier/issues/186#issuecomment-5758496072

   Status of the migration, 2026-09-21:
   
   - The other eight open issues here (#139, #140, #142, #152, #158, #162, 
#165, #177) are closed as superseded; each comment names the maven-executor 
class that covers it.
   - Consumers still on maven-verifier: maven-integration-testing 
(`maven-3.9.x` and `maven-3.10.x`, 644 test files), maven-build-cache-extension 
(130 files, still on 1.8.0), maven-surefire ITs (via the `MavenLauncher` 
fixture), maven-apache-resources, maven-remote-resources-plugin, 
maven-ear-plugin.
   - One blocker for the two large consumers is filed as 
[apache/maven-executor#44](https://github.com/apache/maven-executor/issues/44): 
the only shipped `ExecutorTool` resolves the local repository and artifact 
paths by running a non-ASF plugin, which the `verifyArtifactPresent` and 
`deleteArtifacts` call sites (386 in the core ITs alone) would depend on.
   - MIGRATION.md corrections to follow as a PR: the `verifyErrorFreeLog()` → 
`success()` row, and mappings for `setSystemProperty`, `setLogFileName`, and 
the split stdout/stderr streams.


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