<exclude>packaging.properties</exclude>
									</excludes>
								</resource>
								<resource>
									<directory>${project.basedir}</directory>
									<filtering>true</filtering>
									<includes>
										<include>bin/fess</include>
										<include>bin/fess.in.sh</include>
										<include>bin/generate-thumbnail</include>
										<include>bin/plugin.xml</include>
									</includes>
								</resource>

/**
 * Service for creating {@link PathMatcher} objects that can be used to filter files
 * based on include/exclude patterns. This service provides a clean API for plugins
 * to create path matchers without directly depending on implementation classes.
 * <p>
 * The path matchers created by this service support Maven's traditional include/exclude
 * pattern syntax, which is compatible with the behavior of Maven 3 plugins like

					<excludes>
						<exclude>pom.xml</exclude>
						<exclude>breaking-changes.xml</exclude>
						<exclude>*.md</exclude>
						<exclude>*.sh</exclude>
						<exclude>build.properties</exclude>
						<exclude>docs/**</exclude>
						<exclude>src/test/resources/**</exclude>
						<exclude>**/*.idl</exclude>
						<exclude>**/*.css</exclude>
						<exclude>.*</exclude>
						<exclude>.*/**</exclude>

include(":okhttp-osgi-tests")
include(":okhttp-sse")
include(":okhttp-testing-support")
include(":okhttp-tls")
include(":okhttp-urlconnection")
include(":okhttp-zstd")
include(":samples:compare")
include(":samples:crawler")
include(":samples:guide")
include(":samples:simple-client")
include(":samples:slack")
include(":samples:static-server")
include(":samples:tlssurvey")
include(":samples:unixdomainsockets")

# for any Python version present
pushd /usr/include/x86_64-linux-gnu
for f in $(ls | grep python); do
  # set up symlink for devtoolset-9
  rm -f /dt9/usr/include/x86_64-linux-gnu/$f
  ln -s /usr/include/x86_64-linux-gnu/$f /dt9/usr/include/x86_64-linux-gnu/$f
done
popd

# Python 3.10 include headers fix:
# sysconfig.get_path('include') incorrectly points to /usr/local/include/python

				<include name="dataformat/curvesapi-*" />
				<include name="dataformat/orangesignal-csv-*" />
				<include name="dataformat/poi-*" />
				<include name="dataformat/SparseBitSet-*" />
				<include name="dataformat/stax-api-*" />
				<include name="dataformat/xmlbeans-*" />
				<include name="minhash/guava-*" />
				<include name="minhash/failureaccess-*" />
				<include name="minhash/jspecify-*" />

This is an advanced usage that you might not really need, but it's there in case you do.

## Include an `APIRouter` in another { #include-an-apirouter-in-another }

The same way you can include an `APIRouter` in a `FastAPI` application, you can include an `APIRouter` in another `APIRouter` using:

```Python
router.include_router(other_router)
```

            </jdkToolchain>
            <includes>
              <include>${test.include}</include>
            </includes>
            <!-- By having our own entries here, we also override the default exclusion filter, which excludes all nested classes. -->
            <excludes>
              <!-- https://github.com/google/guava/issues/2840 -->
              <exclude>%regex[.*PackageSanityTests.*.class]</exclude>

            </jdkToolchain>
            <includes>
              <include>${test.include}</include>
            </includes>
            <!-- By having our own entries here, we also override the default exclusion filter, which excludes all nested classes. -->
            <excludes>
              <!-- https://github.com/google/guava/issues/2840 -->
              <exclude>%regex[.*PackageSanityTests.*.class]</exclude>

#include "tensorflow/c/c_api_experimental.h"

#include "absl/strings/substitute.h"
#include "absl/synchronization/notification.h"
#include "tensorflow/c/c_api.h"
#include "tensorflow/c/c_api_internal.h"
#include "tensorflow/c/checkpoint_reader.h"
#include "tensorflow/c/eager/c_api.h"
#include "tensorflow/c/eager/c_api_internal.h"
#include "tensorflow/c/eager/tfe_context_internal.h"