slachiewicz opened a new pull request, #68: URL: https://github.com/apache/maven-verifier-plugin/pull/68
Trims the README to what is still true now that the plugin is retired. The file was the standard "Contributing to ..." guide — fork the repo, open a pull request, run the ITs with `mvn -Prun-its verify`, file a ticket. None of that is actionable on a retired plugin whose repository is about to be archived read only, and leaving it there invites work nobody can accept. What remains: that it is retired, when the project voted, the last released version, and where to ask a question. Deliberately no links to the vote thread, the INFRA ticket or the cleanup PRs — a reader who lands here wants to know whether to use the plugin, not to follow the paperwork. Questions go to the [Maven mailing lists](https://maven.apache.org/mailing-lists.html) page. Also drops the two Jenkins badges: deleting the `Jenkinsfile` removed the `maven-box` job they pointed at, so they can only ever render broken now. The license and Maven Central badges still resolve and stay. Modelled on the README `maven-pdf-plugin` was left with when it was retired. **This wants to merge before INFRA acts on INFRA-28233** — once the repository is archived it is read only and the README is frozen as it stands. <sub>Drafted with Claude — please verify</sub> -- 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]
