elharo commented on code in PR #1821:
URL: https://github.com/apache/maven-site/pull/1821#discussion_r4506170553


##########
content/markdown/guides/mini/guide-lifecycle-filter.md:
##########
@@ -0,0 +1,178 @@
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Skipping Mojo Executions with `maven.lifecycle.filter`
+
+<!--MACRO{toc|fromDepth=2}-->
+
+## Overview
+
+Maven 4.2 introduces a **unified, generic mechanism** to skip any mojo 
execution at
+the command line, independent of whether the plugin itself provides a skip 
property.
+
+The `-Dmaven.lifecycle.filter` user property accepts a comma-separated list of
+**predicates**. Any mojo execution matching at least one predicate is skipped 
at
+runtime: Maven logs the skipped execution at `INFO` level and fires a 
`MojoSkipped`
+execution event so that build listeners are notified.
+
+## Motivation
+
+Traditionally, skipping a mojo execution required a plugin-specific property 
such as

Review Comment:
   The history doesn't matter to the reader/end user. Focus on the 
functionality this provides and the needs it meets in the present. 



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