<excludes>
				<exclude>*</exclude>
			</excludes>
			<filtered>false</filtered>
		</fileSet>
	</fileSets>
	<files>
		<file>
			<source>README.md</source>
			<outputDirectory>fess-${project.version}</outputDirectory>
		</file>
		<file>
			<source>LICENSE</source>
			<outputDirectory>fess-${project.version}</outputDirectory>
		</file>
	</files>

Para mais detalhes sobre a extensão, consulte o README no [repositório do GitHub](https://github.com/fastapi/fastapi-vscode).

## Configuração e Instalação { #setup-and-installation }

            false
        fi
    done
}

@test "No duplicate files on Windows" {
    cat <<EOF
Please rename files so there are no repeats. For example, README.md and
Readme.md would be the same file on Windows. In this test, you would get a
warning for "readme.md" because it makes everything lowercase. There are
repeats of these filename(s) with different casing:
EOF

    @Mock
    private SmbFile smbFile;

    // Provides file names and whether a simple name-based filter should accept them
    private static Stream<Arguments> nameCases() {
        return Stream.of(Arguments.of("readme.txt", true), Arguments.of("notes.log", false), Arguments.of("", false),
                Arguments.of(null, false));
    }

    @Test
    @DisplayName("accept: returns true for directories; verifies isDirectory is invoked")

Pour plus de détails sur l’extension, reportez-vous au README sur le [référentiel GitHub](https://github.com/fastapi/fastapi-vscode).

## Configurer et installer { #setup-and-installation }

Lifecycle transition functionality provided in [bucket lifecycle guide](https://github.com/minio/minio/master/docs/bucket/lifecycle/README.md) allows tiering of content from MinIO object store to public clouds or other MinIO clusters.

│   ├── maven.yml                  # Build and test workflow
│   └── codeql-analysis.yml        # Security analysis
├── pom.xml                        # Maven build configuration
├── README.md                      # Project documentation
└── CLAUDE.md                      # This file
```

## Development Commands

### Build and Test
```bash
# Clean build and run tests
mvn clean test

        try (InputStream is = new ByteArrayInputStream("plain text content".getBytes(StandardCharsets.UTF_8))) {
            assertEquals("application/custom-text", mimeTypeHelper.getContentType(is, "readme.txt"));
        }
    }

set the env. variable `MINIO_KMS_SECRET_KEY` and start/restart the MinIO server. For more details about KES and how
to set it up refer to our [KMS Guide](https://github.com/minio/minio/blob/master/docs/kms/README.md).

Instead of configuring an external KMS you can start with a single key by
setting the env. variable `MINIO_KMS_SECRET_KEY`. It expects the following
format:

```sh
MINIO_KMS_SECRET_KEY=<key-name>:<base64-value>

                Files.createDirectories(tempDir.resolve("shared"));

                // Create some initial files
                Files.writeString(tempDir.resolve("public/readme.txt"), "This is a public share for testing");
                Files.writeString(tempDir.resolve("shared/initial.txt"), "Initial file in shared directory");

                // Configure container with simplified SMB configuration