Debian Codegraph @

maven-enforcer-plugin/src/site/apt/index.apt

raw
1 ~~ Licensed to the Apache Software Foundation (ASF) under one
2 ~~ or more contributor license agreements. See the NOTICE file
3 ~~ distributed with this work for additional information
4 ~~ regarding copyright ownership. The ASF licenses this file
5 ~~ to you under the Apache License, Version 2.0 (the
6 ~~ "License"); you may not use this file except in compliance
7 ~~ with the License. You may obtain a copy of the License at
8 ~~
9 ~~ http://www.apache.org/licenses/LICENSE-2.0
10 ~~
11 ~~ Unless required by applicable law or agreed to in writing,
12 ~~ software distributed under the License is distributed on an
13 ~~ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
14 ~~ KIND, either express or implied. See the License for the
15 ~~ specific language governing permissions and limitations
16 ~~ under the License.
17
18 ------
19 Introduction
20 ------
21 Brian Fox
22 ------
23 2007-03-01
24 ------
25
26 Maven Enforcer Plugin - The Loving Iron Fist of Maven
27
28 The Enforcer plugin provides goals to control certain environmental constraints such as
29 Maven version, JDK version, and OS family along with many more built-in rules and user
30 created rules.
31
32 * Goal Overview
33
34 The Enforcer plugin has a goal:
35
36 *{{{./enforce-mojo.html}enforcer:enforce}} executes rules for each project in a multi-project build.
37
38 * Usage
39
40 General instructions on how to use the Enforcer Plugin can be found on the {{{./usage.html}usage page}}.
41
42 If you have questions regarding the plugin's usage, please have a look at the {{{./faq.html}FAQ}} and feel
43 free to contact the {{{./mailing-lists.html}user mailing list}}. The posts to the mailing list are archived and could
44 already contain the answer to your question as part of an older thread. Hence, it is also worth browsing/searching
45 the {{{./mailing-lists.html}mail archive}}.
46
47 If you feel like the plugin is missing a feature or has a defect, you can file a feature request or bug report in our
48 {{{./issue-management.html}issue tracker}}. When creating a new issue, please provide a comprehensive description of your
49 concern. Especially for fixing bugs it is crucial that the developers can reproduce your problem. For this reason,
50 entire debug logs, POMs or most preferably little demo projects attached to the issue are very much appreciated.
51 Of course, patches are welcome, too. Contributors can check out the project from our
52 {{{./scm.html}source repository}} and will find supplementary information in the
53 {{{/guides/development/guide-helping.html}guide to helping with Maven}}.