</RollingFile>
	</Appenders>

	<Loggers>
		<Logger name="org.codelibs.fess" additivity="false" level="${log.level}">
			<AppenderRef ref="AppFile" />
		</Logger>
		<Root level="${root.log.level}">
			<AppenderRef ref="AppFile" />
		</Root>
	</Loggers>

		</RollingFile>
	</Appenders>

	<Loggers>
		<Logger name="org.codelibs.fess" additivity="false" level="${log.level}">
			<AppenderRef ref="AppFile" />
		</Logger>
		<Root level="${root.log.level}">
			<AppenderRef ref="AppFile" />
		</Root>
	</Loggers>

    // directory with a cycle,
    // /root
    //    /child
    //       /[grandchild -> root]
    Path root = createTempDirectory("ClassPathTest");
    try {
      createFile(root.resolve("some.txt"));
      Path child = createDirectory(root.resolve("child"));
      createSymbolicLink(child.resolve("grandchild"), root);
      assertEquals(

			<AppenderRef ref="AppFile" />
		</Logger>
		<Logger name="fess.log.crawler.stats" additivity="false" level="info">
			<AppenderRef ref="StatsFile" />
		</Logger>
		<Root level="${root.log.level}">
			<AppenderRef ref="AppFile" />
		</Root>
	</Loggers>

 * chain. The chain terminates in a self-signed "root" certificate. Signing certificates in the
 * middle of the chain are called "intermediates". Organizations that offer certificate signing are
 * called certificate authorities (CAs).
 *
 * Browsers and other HTTP clients need a set of trusted root certificates to authenticate their
 * peers. Sets of root certificates are managed by either the HTTP client (like Firefox), or the

# and also repacks libtensorflow-src.jar into a standardized format.

# Helper function to copy a srcjar after moving any source files
# directly under the root to the "maven-style" src/main/java layout
#
# Source files generated by annotation processors appear directly
# under the root of srcjars jars created by bazel, rather than under
# the maven-style src/main/java subdirectory.
#
# Bazel manages annotation generated source as follows: First, it

	@(env bash $(PWD)/buildscripts/verify-healing-empty-erasure-set.sh)
	@(env bash $(PWD)/buildscripts/heal-inconsistent-versions.sh)

verify-healing-with-root-disks: install-race ## verify healing root disks
	@echo "Verify healing with root drives"
	@(env bash $(PWD)/buildscripts/verify-healing-with-root-disks.sh)

verify-healing-with-rewrite: install-race ## verify healing to rewrite old xl.meta -> new xl.meta
	@echo "Verify healing with rewrite"

                            "Failed to read documentation for expression root: " + root, e);
                } catch (XmlPullParserException e) {
                    throw new ExpressionDocumentationException(
                            "Failed to parse documentation for expression root: " + root, e);
                }
            }
        }

        return expressionDocumentation;
    }

forceflag=""
if [ "$1" = "-force" ]; then
	forceflag=-force
	shift
fi

targ="../../go-${GOOS}-${GOARCH}-bootstrap"
if [ -e $targ ]; then
	echo "$targ already exists; remove before continuing"
	exit 2
fi

unset GOROOT
src=$(cd .. && pwd)
echo "#### Copying to $targ"
cp -Rp "$src" "$targ"
cd "$targ"
echo
echo "#### Cleaning $targ"
chmod -R +w .
rm -f .gitignore
if [ -e .git ]; then
	git clean -f -d
fi
echo

** Note **
Previously, site replication required the root credentials of peer sites to be identical. This is no longer necessary because STS tokens are now signed with the site replicator service account credentials, thus allowing flexibility in the independent management of root accounts across sites and the ability to disable root accounts eventually.