~~ 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. ------ Usage ------ Brian Fox ------ Mar 2007 ------ Usage Brief examples on how to use the enforcer goals. * Generic Plugin configuration information See the following links for information about including and configuring plugins in your project: *{{{http://maven.apache.org/guides/mini/guide-configuring-plugins.html}Configuring Plugins}} *{{{http://maven.apache.org/guides/plugin/guide-java-plugin-development.html}Plugin Development}} *{{{http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html}Plugin Prefix}} [] * The <<>> mojo This goal is meant to be bound to a lifecycle phase and configured in your <<>>. The enforcers execute the configured rules to check for certain constraints. The available built-in rules are described {{{../enforcer-rules/index.html}here}}. Besides the rules to execute, these goals support three options: * {{{./enforce-mojo.html#skip}skip}} - a quick way to skip checks via a profile or using <<<-Denforcer.skip=true>>> from the command line. * {{{./enforce-mojo.html#fail}fail}} - if the goal should fail the build when a rule fails. The default is <<>>. If false, the errors will be logged as warnings. * {{{./enforce-mojo.html#failFast}failFast}} - if the goal should stop checking after the first failure. The default is <<>>. [] Each rule to be executed should be added to the rules element along with the specific configuration for that rule. As of version 1.4, you may add a <<>> element to the rules. Valid values are <<>> and <<>>. When <<>> <<>> is specified, the rule will only spit out a warning but will not fail the build. Sample Plugin Configuration: +---+ [...] org.apache.maven.plugins maven-enforcer-plugin ${project.version} enforce-versions enforce WARN org.apache.maven.plugins:maven-verifier-plugin Please consider using the maven-invoker-plugin (http://maven.apache.org/plugins/maven-invoker-plugin/)! 2.0.6 1.5 unix [...] +---+ * The <<>> mojo This goal is used to determine the current information as detected by the standard rules: +---+ mvn enforcer:display-info ... [enforcer:display-info] Maven Version: 2.0.6 JDK Version: 1.5.0_11 normalized as: 1.5.0-11 OS Info: Arch: x86 Family: windows Name: windows xp Version: 5.1 +---+