Description

A check that makes sure that a specified pattern exists, exists less than a set number of times, or does not exist in the file.

This check combines all the functionality provided by RegexpHeader except supplying the regular expression from a file.

It differs from them in that it works in multiline mode. Its regular expression can span multiple lines and it checks this against the whole file at once. The others work in singleline mode. Their single or multiple regular expressions can only span one line. They check each of these against each line in the file in turn.

Note: Because of the different mode of operation there may be some changes in the regular expressions used to achieve a particular end.

In multiline mode...

• ^ means the beginning of a line, as opposed to beginning of the input.
• For beginning of the input use \A.
• $ means the end of a line, as opposed to the end of the input.
• For end of input use \Z.
• Each line in the file is terminated with a line feed character.

Note: Not all regular expression engines are created equal. Some provide extra functions that others do not and some elements of the syntax may vary. This check makes use of the java.util.regex package; please check its documentation for details of how to construct a regular expression to achieve a particular goal.

Note: When entering a regular expression as a parameter in the XML config file you must also take into account the XML rules. e.g. if you want to match a < symbol you need to enter &lt;. The regular expression should be entered on one line.

Properties

Examples

The following examples are mainly copied from the other 3 checks mentioned above, to show how the same results can be achieved using this check in place of them.

To use like Required Regexp check:

An example of how to configure the check to make sure a copyright statement is included in the file:

The statement.

          // This code is copyrighted
        

The check.

          <module name="Regexp">
          <property name="format" value="// This code is copyrighted"/>
          </module>
        

Your statement may be multiline.

          // This code is copyrighted
          // (c) MyCompany
        

Then the check would be.

          <module name="Regexp">
          <property name="format" value="// This code is copyrighted\n// \(c\) MyCompany"/>
          </module>
        

Note: To search for parentheses () in a regular expression you must escape them like \(\). This is required by the regexp engine, otherwise it will think they are special instruction characters.

And to make sure it appears only once:

          <module name="Regexp">
          <property name="format" value="// This code is copyrighted\n// \(c\) MyCompany"/>
          <property name="duplicateLimit" value="0"/>
          </module>
        

It can also be useful to attach a meaningful message to the check:

          <module name="Regexp">
          <property name="format" value="// This code is copyrighted\n// \(c\) MyCompany"/>
          <property name="message" value="Copyright"/>
          </module>
        

To use like illegal regexp check:

An example of how to configure the check to make sure there are no calls to System.out.println:

          <module name="Regexp">
          <!-- . matches any character, so we need to escape it and use \. to match dots. -->
          <property name="format" value="System\.out\.println"/>
          <property name="illegalPattern" value="true"/>
          </module>
        

You may want to make the above check ignore comments, like this:

          <module name="Regexp">
          <property name="format" value="System\.out\.println"/>
          <property name="illegalPattern" value="true"/>
          <property name="ignoreComments" value="true"/>
          </module>
        

An example of how to configure the check to find trailing whitespace at the end of a line:

          <module name="Regexp">
          <property name="format" value="[ \t]+$"/>
          <property name="illegalPattern" value="true"/>
          <property name="message" value="Trailing whitespace"/>
          </module>
        

An example of how to configure the check to find case-insensitive occurrences of "debug":

          <module name="Regexp">
          <property name="format" value="(?i)debug"/>
          <property name="illegalPattern" value="true"/>
          </module>
        

Note: The (?i) at the beginning of the regular expression tells the regexp engine to ignore the case.

There is also a feature to limit the number of errors reported. When the limit is reached the check aborts with a message reporting that the limit has been reached. The default limit setting is 100, but this can be change as shown in the following example.

          <module name="Regexp">
          <property name="format" value="(?i)debug"/>
          <property name="illegalPattern" value="true"/>
          <property name="errorLimit" value="1000"/>
          </module>
        

To use like RegexpHeader :

To configure the check to verify that each file starts with the following multiline header.

Note the following:

• \A means the start of the file.
• The date can be any 4 digit number.

          // Copyright (C) 2004 MyCompany
          // All rights reserved
        

          <module name="Regexp">
          <property
          name="format"
          value="\A// Copyright \(C\) \d\d\d\d MyCompany\n// All rights reserved"/>
          </module>
        

A more complex example. Note how the import and javadoc multilines are handled, there can be any number of them.

          ///////////////////////////////////////////////////////////////////////
          // checkstyle:
          // Checks Java source code for adherence to a set of rules.
          // Copyright (C) 2004  Oliver Burn
          // Last modification by $Author A.N.Other$
          ///////////////////////////////////////////////////////////////////////

          package com.puppycrawl.checkstyle;

          import java.util.thing1;
          import java.util.thing2;
          import java.util.thing3;

          /**
          * javadoc line 1
          * javadoc line 2
          * javadoc line 3
          */
        

          <module name="Regexp">
          <property
          name="format"
          value="\A/{71}\n// checkstyle:\n// Checks Java source code for
          adherence to a set of rules\.\n// Copyright \(C\) \d\d\d\d  Oliver Burn\n
          // Last modification by \$Author.*\$\n/{71}\n\npackage [\w\.]*;\n\n
          (import [\w\.]*;\n)*\n/\*\*\n( \*[^/]*\n)* \*/"/>
          </module>
        

More examples:

The next 2 examples deal with the following example Java source file:

          /*
          * PID.java
          *
          * Copyright (c) 2001 ACME
          * 123 Some St.
          * Somewhere.
          *
          * This software is the confidential and proprietary information of ACME.
          * ("Confidential Information"). You shall not disclose such
          * Confidential Information and shall use it only in accordance with
          * the terms of the license agreement you entered into with ACME.
          *
          * $Log: config_misc.xml,v $
          * Revision 1.7  2007/01/16 12:16:35  oburn
          * Removing all reference to mailing lists
          *
          * Revision 1.6  2005/12/25 16:13:10  o_sukhodolsky
          * Fix for rfe 1248106 (TYPECAST is now accepted by NoWhitespaceAfter)
          *
          * Fix for rfe 953266 (thanks to Paul Guyot (pguyot) for submitting patch)
          * IllegalType can be configured to accept some abstract classes which
          * matches to regexp of illegal type names (property legalAbstractClassNames)
          *
          * TrailingComment now can be configured to accept some trailing comments
          * (such as NOI18N) (property legalComment, rfe 1385344).
          *
          * Revision 1.5  2005/11/06 11:54:12  oburn
          * Incorporate excellent patch [ 1344344 ] Consolidation of regexp checks.
          *
          * Revision 1.3.8.1  2005/10/11 14:26:32  someone
          * Fix for bug 251.  The broken bit is fixed
          */

          package com.acme.tools;

          import com.acme.thing1;
          import com.acme.thing2;
          import com.acme.thing3;

          /**
          *
          * <P>
          *   <I>This software is the confidential and proprietary information of
          *   ACME (<B>"Confidential Information"</B>). You shall not
          *   disclose such Confidential Information and shall use it only in
          *   accordance with the terms of the license agreement you entered into
          *   with ACME.</I>
          * </P>
          *
          * &#169; copyright 2002 ACME
          *
          * @author   Some Body
          */
          public class PID extends StateMachine implements WebObject.Constants {

          /** javadoc. */
          public static final int A_SETPOINT = 1;
          .
          .
          .
          } // class PID
        

This checks for the presence of the header, the first 16 lines.

Note the following:

• Line 2 and 13 contain the file name. These are checked to make sure they are the same, and that they match the class name.
• The date can be any 4 digit number.

          <module name="Regexp">
          <property
          name="format"
          value="\A/\*\n \* (\w*)\.java\n \*\n \* Copyright \(c\)
          \d\d\d\d ACME\n \* 123 Some St\.\n \* Somewhere\.\n \*\n
          \* This software is the confidential and proprietary information
          of ACME\.\n \* \(&quot;Confidential Information&quot;\)\. You
          shall not disclose such\n \* Confidential Information and shall
          use it only in accordance with\n \* the terms of the license
          agreement you entered into with ACME\.\n \*\n
          \* \$Log: config_misc\.xml,v $
          \* Revision 1\.7  2007/01/16 12:16:35  oburn
          \* Removing all reference to mailing lists
          \* \
          \* Revision 1.6  2005/12/25 16:13:10  o_sukhodolsky
          \* Fix for rfe 1248106 \(TYPECAST is now accepted by NoWhitespaceAfter\)
          \* \
          \* Fix for rfe 953266 \(thanks to Paul Guyot \(pguyot\) for submitting patch\)
          \* IllegalType can be configured to accept some abstract classes which
          \* matches to regexp of illegal type names \(property legalAbstractClassNames\)
          \*
          \* TrailingComment now can be configured to accept some trailing comments
          \* \(such as NOI18N\) \(property legalComment, rfe 1385344\).
          \*
          \* Revision 1.5  2005/11/06 11:54:12  oburn
          \* Incorporate excellent patch \[ 1344344 \] Consolidation of regexp checks.
          \* \\n(.*\n)*([\w|\s]*( class | interface )\1)"/>
          <property name="message" value="Correct header not found"/>
          </module>
        

This checks for the presence of a copyright notice within the class javadoc, lines 24 to 37.

          <module name="Regexp">
          <property
          name="format"
          value="(/\*\*\n)( \*.*\n)*( \* &lt;P&gt;\n \*   &lt;I&gt;
          This software is the confidential and proprietary information of\n
          \*   ACME \(&lt;B&gt;&quot;Confidential Information&quot;&lt;/B&gt;
          \)\. You shall not\n \*   disclose such Confidential Information
          and shall use it only in\n \*   accordance with the terms of the
          license agreement you entered into\n \*   with ACME\.&lt;/I&gt;\n
          \* &lt;/P&gt;\n \*\n \* &#169; copyright \d\d\d\d ACME\n
          \*\n \* @author .*)(\n\s\*.*)*/\n[\w|\s]*( class | interface )"/>
          <property name="message" value="Copyright in class/interface Javadoc"/>
          <property name="duplicateLimit" value="0"/>
          </module>
        

Note: To search for things that mean something in XML, like < you need to escape them like &lt;. This is required so the XML parser does not act on them, but instead passes the correct character to the regexp engine.

Example of Usage

• Checkstyle Style

Error Messages

• duplicate.regexp
• illegal.regexp
• required.regexp

All messages can be customized if the default message doesn't suite you. Please see the documentation to learn how to.

Package

com.puppycrawl.tools.checkstyle.checks.regexp

Parent Module

TreeWalker

Description

A check for detecting that matches across multiple lines. Works with any file type.

Rationale: This check can be used to when the regular expression can be span multiple lines.

Properties

Examples

To configure the check to find calls to print to the console:

<module name="RegexpMultiline">
  <property name="format"
   value="System\.(out)|(err)\.print(ln)?\("/>
</module>
        

Example of Usage

• Checkstyle Style

Error Messages

• regexp.StackOverflowError
• regexp.empty
• regexp.exceeded
• regexp.minimum

All messages can be customized if the default message doesn't suite you. Please see the documentation to learn how to.

Package

com.puppycrawl.tools.checkstyle.checks.regexp

Parent Module

Checker

Description

Implementation of a check that looks for a file name and/or path match (or mis-match) against specified patterns. It can also be used to verify files match specific naming patterns not covered by other checks (Ex: properties, xml, etc.).

When customizing the check, the properties are applied in a specific order. The fileExtensions property first picks only files that match any of the specific extensions supplied. Once files are matched against the fileExtensions, the match property is then used in conjuction with the patterns to determine if the check is looking for a match or mis-match on those files. If the fileNamePattern is supplied, the matching is only applied to the fileNamePattern and not the folderPattern. If no fileNamePattern is supplied, then matching is applied to the folderPattern only and will result in all files in a folder to be reported on violations. If no folderPattern is supplied, then all folders that checkstyle finds are examined for violations. The ignoreFileNameExtensions property drops the file extension and applies the fileNamePattern only to the rest of file name. For example, if the file is named 'test.java' and this property is turned on, the pattern is only applied to 'test'.

If this check is configured with no properties, then the default behavior of this check is to report file names with spaces in them. When at least one pattern property is supplied, the entire check is under the user's control to allow them to fully customize the behavior.

It is recommended that if you create your own pattern, to also specify a custom error message. This allows the error message printed to be clear what the violation is, especially if multiple RegexpOnFilename checks are used. Argument 0 for the message populates the check's folderPattern. Argument 1 for the message populates the check's fileNamePattern. The file name is not passed as an argument since it is part of CheckStyle's default error messages.

Properties

Examples

To configure the check to report file names that contain a space:

<module name="RegexpOnFilename"/>
        

To configure the check to force picture files to not be 'gif':

<module name="RegexpOnFilename">
  <property name="fileNamePattern" value="\.gif$"/>
</module>
        

OR:

<module name="RegexpOnFilename">
  <property name="fileNamePattern" value="."/>
  <property name="fileExtensions" value="gif"/>
</module>
        

To configure the check to only allow property and xml files to be located in the resource folder:

<module name="RegexpOnFilename">
  <property name="folderPattern" value="[\\/]src[\\/]\w+[\\/]resources[\\/]"/>
  <property name="match" value="false"/>
  <property name="fileExtensions" value="properties, xml"/>
</module>
        

To configure the check to only allow Java and XML files in your folders use the below.

<module name="RegexpOnFilename">
  <property name="fileNamePattern" value="\.(java|xml)$"/>
  <property name="match" value="false"/>
</module>
        

To configure the check to only allow Java and XML files only in your source folder and ignore any other folders:
Note: 'folderPattern' must be specified if checkstyle is analyzing more than the normal source folder, like the 'bin' folder where class files can be located.

<module name="RegexpOnFilename">
  <property name="folderPattern" value="[\\/]src[\\/]"/>
  <property name="fileNamePattern" value="\.(java|xml)$"/>
  <property name="match" value="false"/>
</module>
        

To configure the check to only allow file names to be camel case:

<module name="RegexpOnFilename">
  <property name="fileNamePattern" value="^([A-Z][a-z0-9]+\.?)+$"/>
  <property name="match" value="false"/>
  <property name="ignoreFileNameExtensions" value="true"/>
</module>
        

Example of Usage

• Checkstyle Style

Error Messages

• regexp.filename.match
• regexp.filename.mismatch

All messages can be customized if the default message doesn't suite you. Please see the documentation to learn how to.

Package

com.puppycrawl.tools.checkstyle.checks.regexp

Parent Module

Checker

Description

A check for detecting single lines that match a supplied regular expression. Works with any file type.

Rationale: This check can be used to prototype checks and to find common bad practice such as calling ex.printStacktrace(), System.out.println(), System.exit(), etc.

Properties

Examples

To configure the check to find trailing whitespace at the end of a line:

<module name="RegexpSingleline">
  <!-- \s matches whitespace character, $ matches end of line. -->
  <property name="format" value="\s+$"/>
</module>
        

To configure the check to find trailing whitespace at the end of a line, with some slack of allowing two occurrences per file:

<module name="RegexpSingleline">
  <property name="format" value="\s+$"/>
  <!-- next line not required as 0 is the default -->
  <property name="minimum" value="0"/>
  <property name="maximum" value="2"/>
</module>
        

An example of how to configure the check to make sure a copyright statement is included in the file:

<module name="RegexpSingleline">
  <property name="format" value="This file is copyrighted"/>
  <property name="minimum" value="1"/>
  <!--  Need to specify a maximum, so 10 times is more than enough. -->
  <property name="maximum" value="10"/>
</module>
        

Example of Usage

• Checkstyle Style
• Sun Style

Error Messages

• regexp.exceeded

• regexp.minimum

All messages can be customized if the default message doesn't suite you. Please see the documentation to learn how to.

Package

com.puppycrawl.tools.checkstyle.checks.regexp

Parent Module

Checker

Description

This class is variation on RegexpSingleline for detecting single lines that match a supplied regular expression in Java files. It supports suppressing matches in Java comments.

Properties

Examples

To configure the check for calls to System.out.println, except in comments:

<module name="RegexpSinglelineJava">
    <!-- . matches any character, so we need to
         escape it and use \. to match dots. -->
  <property name="format" value="System\.out\.println"/>
  <property name="ignoreComments" value="true"/>
</module>
        

To configure the check to find case-insensitive occurrences of "debug":

<module name="RegexpSinglelineJava">
    <property name="format" value="debug"/>
    <property name="ignoreCase" value="true"/>
</module>
        

Example of Usage

• Checkstyle Style

Error Messages

• regexp.exceeded

• regexp.minimum

All messages can be customized if the default message doesn't suite you. Please see the documentation to learn how to.

Package

com.puppycrawl.tools.checkstyle.checks.regexp

Parent Module

TreeWalker