<plugin>
                <groupId>org.jetbrains.teamcity</groupId>
                <artifactId>teamcity-configs-maven-plugin</artifactId>
                <version>${teamcity.dsl.version}</version>
                <configuration>
                    <format>kotlin</format>
                    <dstDir>target/generated-configs</dstDir>
                    <contextParameters>
                        <Branch>${dslContextParameter.branch}</Branch>

                   animal-sniffer. And that would be fine for our -jre builds:
                   If we're building with JDK8, then clearly we're sticking to
                   JDK8 APIs. However, I assume (but did not confirm) that we'd
                   have the same issue with our -android builds, which need
                   animal-sniffer so that they can check that we're sticking to
                   JDK6-like APIs.

									<includes>
										<include>logging.properties</include>
										<include>tomcat_config.properties</include>
									</includes>
								</source>
								<source>
									<location>${project.build.directory}/fess/WEB-INF/classes</location>
									<includes>
										<include>fess_config.properties</include>
										<include>fess_env_crawler.properties</include>

            <!-- Even after we stop using JSR305 annotations in our own code, we'll want this link so that NullPointerTester's docs can link to @CheckForNull and friends... at least once we start using this config for guava-testlib. -->
            <offlineLink>
              <url>https://static.javadoc.io/com.google.code.findbugs/jsr305/3.0.1/</url>
              <location>${project.basedir}/javadoc-link/jsr305</location>