Maven enforcer Plugin: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 14: Line 14:
The list of rules the plugin can enforce is specified here: https://maven.apache.org/enforcer/enforcer-rules/index.html
The list of rules the plugin can enforce is specified here: https://maven.apache.org/enforcer/enforcer-rules/index.html


The enforcer plugin binds to the [[Maven_Concepts_-_Lifecycle#validate|validate]] phase, which is the first one.
The enforcer plugin binds to the [[Maven_Concepts_-_Lifecycle#validate|validate]] phase, which is the first phase in the lifecycle.


=Examples=
=Examples=

Revision as of 01:10, 31 May 2016

External

Internal

Overview

The plugin checks rules and warns or fails the build if conditions are not met.

The list of rules the plugin can enforce is specified here: https://maven.apache.org/enforcer/enforcer-rules/index.html

The enforcer plugin binds to the validate phase, which is the first phase in the lifecycle.

Examples

Fail if Files Do Not Exist

Works with both files and directories. For directories, use the same <requireFilesExist>.

<project>
  [...]
  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-enforcer-plugin</artifactId>
        <executions>
          <execution>
            <id>enforce-file-exists</id>
            <goals>
              <goal>enforce</goal>
            </goals>
            <configuration>
              <rules>
                <requireFilesExist>
                  <files>
                   <file>${project.build.outputDirectory}/foo.txt</file>
                   <file>${project.build.outputDirectory}/foo2.txt</file>
                  </files>
                </requireFilesExist>
              </rules>
              <fail>true</fail>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>
  [...]
</project>