The checkModificationExcludes option does currently only allow the definition single files to be excluded from the SCM modification check. If this option is defined, all files anywhere in the maven project structure with the specified name will be excluded from the check. It is currently not possible to exclude files only within a specific directory or to exclude classes of files, i.e. all files matching a specific file name pattern.
If the checkModificationExcludes option allowed the definition of file and directory patterns, these things would be possible.
Example 1: I'd like to exclude a test resource src/test/resources/foo.properties from the modification check but the real foo.properties in src/main/resources should still be checked.
Example 2: I'd like to exclude all properties files with the prefix bar from the modification check:
The attached patch modifies the ScmCheckModificationsPhase to use the DirectoryScanner from plexus-utils instead of doing a strict file name comparison. The patch does not provide more unit tests for this feature but it adjusts the existing tests to run without any failures.