* @param includes the patterns of files to include, or null/empty for including all files
     * @param excludes the patterns of files to exclude, or null/empty for no exclusion
     * @param useDefaultExcludes whether to augment excludes with default SCM exclusion patterns
     * @return a PathMatcher that can be used to test if paths should be included
     * @throws NullPointerException if baseDirectory is null
     */
    @Nonnull

        // we always include all source files, and exclude what should not be checked
        .include("**")
        // exclude known binary extensions
        .exclude("**/*.gz")
        .exclude("**/*.ico")
        .exclude("**/*.jar")
        .exclude("**/*.zip")
        .exclude("**/*.jks")
        .exclude("**/*.crt")
        .exclude("**/*.keystore")
        .exclude("**/*.png")

  - The calculations for Pod topology spread skew now excludes nodes that
  don't match the node affinity/selector. This may lead to unschedulable pods if you previously had pods
  matching the spreading selector on those excluded nodes (not matching the node affinity/selector),

    Source of the work are being offered to the general public at no
    charge under subsection 6d.

  A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.

  A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,

- When a PreFilterResult filters out certain Nodes, the scheduling framework now categorizes them as rejected via `UnschedulableAndUnresolvable`. Consequently, these nodes are excluded from the candidates for the preemption process. Additionally, this update corrects how the scheduling framework handles the Unschedulable status from PreFilter. Previously, if PreFilter returned `Unschedulable`, it could lead to an unexpected abortion in the preemption process, which shouldn't...

          </excludes>
        </configuration>
      </plugin>
      <plugin>
        <artifactId>maven-source-plugin</artifactId>
        <configuration>
          <excludes>
            <!-- 3. Don't include it in the source jar (since it's really more of a "test" than it is production code). -->
            <exclude>**/ForceGuavaCompilation*</exclude>

			<outputDirectory>fess-${project.version}/logs</outputDirectory>
			<excludes>
				<exclude>*</exclude>
			</excludes>
			<filtered>false</filtered>
		</fileSet>
		<!-- temp -->
		<fileSet>
			<directory>src/main/assemblies/files</directory>
			<outputDirectory>fess-${project.version}/temp</outputDirectory>
			<excludes>
				<exclude>*</exclude>
			</excludes>
			<filtered>false</filtered>
		</fileSet>
		<!-- es/modules -->

      <outputDirectory>/</outputDirectory>
      <excludes>
        <exclude>%regex[(?!((?!target/)[^/]+/)*src/).*target.*]</exclude>
        <exclude>**/*.log</exclude>
        <exclude>**/.gitignore</exclude>
        <exclude>**/.gitattributes</exclude>
        <exclude>init-git-svn.sh</exclude>
        <exclude>**/.repository/**</exclude>
        <exclude>**/.classpath</exclude>
        <exclude>**/.project</exclude>

              <Multi-Release>true</Multi-Release>
            </manifestEntries>
          </archive>
          <excludes>
            <exclude>/module-info.class</exclude>
            <exclude>META-INF/versions/9/com/google/common/util/concurrent/internal/*.class</exclude>
          </excludes>
        </configuration>
      </plugin>
      <plugin>
        <artifactId>maven-source-plugin</artifactId>
      </plugin>

  - the node label `alpha.service-controller.kubernetes.io/exclude-balancer` which excludes a node from cloud load balancers (using Service Type=LoadBalancer) is deprecated in favor of `node.kubernetes.io/exclude-balancer`. Support for `alpha.service-controller.kubernetes.io/exclude-balancer` will be removed in v1.18.

- Features: