for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for

		<get dest="${target.dir}/mydbflute.zip">
			<url url="${mydbflute.url}" />
		</get>
		<unzip dest="${mydbflute.dir}" src="${target.dir}/mydbflute.zip">
			<patternset>
				<include name="lastaflute-example-waterfront-${branch.name}/mydbflute/dbflute-1.x/**" />
			</patternset>
			<cutdirsmapper dirs="2" />
		</unzip>
	</target>

    for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for

            "The file system is full.", "All pipe instances are busy.", "All pipe instances are busy.", "The pipe state is invalid.",
            "All pipe instances are busy.", "No process is on the other end of the pipe.", "The pipe is being closed.",
            "Waiting for a process to open the other end of the pipe.", "File is a directory.", "A duplicate name exists on the network.",

    for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for

    for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for

   * semicolon</a>, rather than the ampersand, as a parameter delimiter. Nevertheless, we recommend
   * using the ampersand unless you must interoperate with systems that require semicolons.
   *
   * <p><b>Note:</b> Unlike other escapers, URL escapers produce <a
   * href="https://url.spec.whatwg.org/#percent-encode">uppercase</a> hexadecimal sequences.
   *
   */
  public static Escaper urlFormParameterEscaper() {

    for details.

    The summary is that it ignores one file in favor of the other.
    util.concurrent, like nearly all our packages, has two .gwt.xml files: one
    for prod and one for tests. However, unlike our other packages, as of this
    writing it has test supersource but no prod supersource.

    GWT happens to use the prod .gwt.xml, so it looks for no supersource for

    private final Pipe pipe = new Pipe(8192);
    private final BufferedSink sink = Okio.buffer(pipe.sink());

    public BufferedSink sink() {
      return sink;
    }

    @Override public MediaType contentType() {
      return MEDIA_TYPE_MARKDOWN;
    }

    @Override public void writeTo(BufferedSink sink) throws IOException {
      sink.writeAll(pipe.source());
    }
  }

    private SmbPipeHandle mockSmbPipeHandle;
    @Mock
    private BufferCache mockBufferCache;

    private static final String TEST_URL = "ncacn_np:server[\\pipe\\test]";
    private static final String TEST_SERVER = "server";
    private static final String TEST_ENDPOINT = "\\pipe\\test";

    @BeforeEach
    void setUp() throws IOException {
        // Setup mock behavior with lenient stubbing to avoid UnnecessaryStubbingException