You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by sl...@apache.org on 2026/08/09 12:40:22 UTC
(maven-verifier-plugin) branch master updated: Cut the README down to the retirement notice
This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-verifier-plugin.git
The following commit(s) were added to refs/heads/master by this push:
new 106ba17 Cut the README down to the retirement notice
106ba17 is described below
commit 106ba1758d2e75f6b75dc6c04780c65c4ce22318
Author: Sylwester Lachiewicz <sl...@apache.org>
AuthorDate: Sun Aug 9 14:37:56 2026 +0200
Cut the README down to the retirement notice
The file was the standard "Contributing to ..." guide: how to fork, how to
open a pull request, how to run the ITs, where to file a ticket. None of that
is actionable on a plugin the project has retired and whose repository is
about to be archived read only.
What remains is what a visitor actually needs: that it is retired, the last
released version, and where to ask a question. The two Jenkins badges go with
it, since deleting the Jenkinsfile removed the job they pointed at, and the
license and Maven Central badges still resolve.
Modelled on the README maven-pdf-plugin was left with when it was retired.
Generated-by: Claude Opus 5 (1M context)
---
README.md | 67 +++++++++------------------------------------------------------
1 file changed, 9 insertions(+), 58 deletions(-)
diff --git a/README.md b/README.md
index 6434314..b1dafbd 100644
--- a/README.md
+++ b/README.md
@@ -14,70 +14,21 @@
See the License for the specific language governing permissions and
limitations under the License.
-->
-Contributing to [Apache Maven Verifier Plugin](https://maven.apache.org/plugins/maven-verifier-plugin/)
-======================
+Contributing to [Apache Maven Stage Plugin](https://maven.apache.org/plugins/maven-stage-plugin/)
+RETIRED - [Apache Maven Verifier Plugin](https://maven.apache.org/plugins/maven-verifier-plugin/)
+=================================================================================================
[][license]
[](https://search.maven.org/artifact/org.apache.maven.plugins/maven-verifier-plugin)
-[][build]
-[][test-results]
+This plugin is retired. It is no longer maintained.
+---------------------------------------------------
-You have found a bug, or you have an idea for a cool new feature? Contributing
-code is a great way to give something back to the open source community. Before
-you dig right into the code, there are a few guidelines that we need
-contributors to follow so that we can have a chance of keeping on top of
-things.
+The Apache Maven project voted to retire it on 2025-11-29. No further releases
+will be made and the repository no longer accepts contributions. The last released
+version is 1.1, which remains available from Maven Central.
-Getting Started
----------------
-
-+ Make sure you have a [GitHub account](https://github.com/signup/free).
-+ If you're planning to implement a new feature, it makes sense to discuss your changes
- on the [dev list][ml-list] first.
- This way you can make sure you're not wasting your time on something that isn't
- considered to be in Apache Maven's scope.
-+ Submit a ticket for your issue, assuming one does not already exist.
- + Clearly describe the issue, including steps to reproduce when it is a bug.
- + Make sure you fill in the earliest version that you know has the issue.
-+ Fork the repository on GitHub.
-
-Making and Submitting Changes
---------------
-
-We accept Pull Requests via GitHub. The [developer mailing list][ml-list] is the
-main channel of communication for contributors.
-There are some guidelines which will make applying PRs easier for us:
-+ Create a topic branch from where you want to base your work (this is usually the master branch).
- Push your changes to a topic branch in your fork of the repository.
-+ Make commits of logical units.
-+ Respect the original code style: by using the same [codestyle][code-style],
- patches should only highlight the actual difference, not being disturbed by any formatting issues:
- + Only use spaces for indentation.
- + Create minimal diffs - disable on save actions like reformat source code or organize imports.
- If you feel the source code should be reformatted, create a separate PR for this change.
- + Check for unnecessary whitespace with `git diff --check` before committing.
-+ Make sure you have added the necessary tests (JUnit/IT) for your changes.
-+ Run all the tests with `mvn -Prun-its verify` to assure nothing else was accidentally broken.
-+ Submit a pull request to the repository in the Apache organization.
-
-If you plan to contribute on a regular basis, please consider filing a [contributor license agreement][cla].
-
-Additional Resources
---------------------
-
-+ [Contributing patches](https://maven.apache.org/guides/development/guide-maven-development.html#Creating_and_submitting_a_patch)
-+ [Contributor License Agreement][cla]
-+ [General GitHub documentation](https://help.github.com/)
-+ [GitHub pull request documentation](https://help.github.com/send-pull-requests/)
-+ [Apache Maven X Account](https://x.com/ASFMavenProject)
-+ [Apache Maven Bluesky Account](https://bsky.app/profile/maven.apache.org)
-+ [Apache Maven Mastodon Account](https://mastodon.social/deck/@ASFMavenProject@fosstodon.org)
+If you have questions, please [contact the Apache Maven development team][ml-list].
[license]: https://www.apache.org/licenses/LICENSE-2.0
[ml-list]: https://maven.apache.org/mailing-lists.html
-[code-style]: https://maven.apache.org/developers/conventions/code.html
-[cla]: https://www.apache.org/licenses/#clas
-[maven-wiki]: https://cwiki.apache.org/confluence/display/MAVEN/Index
-[test-results]: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-verifier-plugin/job/master/lastCompletedBuild/testReport/
-[build]: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-verifier-plugin/job/master/