* For example, for the Java language, the pattern includes all files with the {@code .java} suffix.</p>
     *
     * @see java.nio.file.FileSystem#getPathMatcher(String)
     */
    default List<String> includes() {
        return List.of();
    }

    /**
     * {@return the list of patterns for the files to exclude}

        assertFalse(locator("smb://server/share/").isIPC());
    }

    @Test
    @DisplayName("Type detection covers filesystem/share/IPC/workgroup/server")
    void testGetType() throws Exception {
        // Filesystem when there is a path beyond share
        assertEquals(SmbConstants.TYPE_FILESYSTEM, locator("smb://server/share/path").getType());

        // Named pipe for IPC$ root

@Timeout(30)
open class TrailersTest {
  private val fileSystem = FakeFileSystem()

  @JvmField
  @RegisterExtension
  val platform = PlatformRule()

  @RegisterExtension
  val clientTestRule = OkHttpClientTestRule()

  @StartStop
  private val server = MockWebServer()

  private var client =
    clientTestRule
      .newClientBuilder()
      .cache(Cache(fileSystem, "/cache/".toPath(), Long.MAX_VALUE))
      .build()

   * behavior that the {@link File} API does not already account for. For example, on NTFS it will
   * report {@code "txt"} as the extension for the filename {@code "foo.exe:.txt"} even though NTFS
   * will drop the {@code ":.txt"} part of the name when the file is actually created on the
   * filesystem due to NTFS's <a

     */
    public final void setFileInfoClass(final byte fileInfoClass) {
        setInfoType(Smb2Constants.SMB2_0_INFO_FILE);
        this.fileInfoClass = fileInfoClass;
    }

    /**
     * Sets the filesystem information class for the query
     *
     * @param fileInfoClass
     *            the fileInfoClass to set
     */
    public final void setFilesystemInfoClass(final byte fileInfoClass) {

        case FileSystemInformation.FS_SIZE_INFO -> new FileFsSizeInformation();
        default -> throw new SMBProtocolDecodingException("Unknown filesystem info class " + infoClass);
        };
    }

    /**
     * @param infoClass
     * @return
     * @throws SMBProtocolDecodingException
     */

 * Maven POM files and resolving related project POMs.
 *
 * <p>The interface provides two types of sources:</p>
 * <ul>
 *   <li>Build sources: Used for POM files of projects being built by Maven in the filesystem.
 *       These sources support resolving related POMs using the {@link ModelLocator}.</li>
 *   <li>Resolved sources: Used for artifacts that have been resolved by Maven from repositories

 * all the details of accessing the underlying content while providing
 * a uniform API to consumers.
 * <p>
 * Sources can represent:
 * <ul>
 *   <li>Local filesystem files</li>
 *   <li>In-memory content</li>
 *   <li>Database entries</li>
 *   <li>Network resources</li>
 * </ul>
 *
 * @since 4.0.0
 * @see org.apache.maven.api.services.ProjectBuilder#build(Session, Source)

            directoryPermissions =
                () -> {
                  throw new IOException("unrecognized FileSystem type " + FileSystems.getDefault());
                };
      }
    }

    private static PermissionSupplier userPermissions() {
      try {
        UserPrincipal user =
            FileSystems.getDefault()
                .getUserPrincipalLookupService()
                .lookupPrincipalByName(getUsername());

   * behavior that the {@link File} API does not already account for. For example, on NTFS it will
   * report {@code "txt"} as the extension for the filename {@code "foo.exe:.txt"} even though NTFS
   * will drop the {@code ":.txt"} part of the name when the file is actually created on the
   * filesystem due to NTFS's <a