exploded-war-child-copy-spec-example.graffle ApplicationVersionco.omnigroup.OmniGraffle7.MacAppStore186.3ColorProfilesdataAA/gAAAAUbWVhcwAABAwAAA+wEBAQcBDQETARkBHwElA+gIDAgwCFAIdAiYCLwI4A+wD+QQGBBMEIAQtBDsESARVB+BIwEmgSoBLYExATTBOEE+BQ0FHAUrBToFSQVYBWcF/B9IH5Qf4CAsIHwgyCEYI+EL+QwSDCoMQwxcDHUMjgynD/DpsOtg7SDu4PCQ8lD0EP/PD+wQCRAmEEMQYRB+EJsQuRDXEPURExExEU8R+UUBhQnFEkUahSLFK0Uzh/cYGxhAGGUYihivGNUY+hkgGUUZaxmRGbcZ3RoEG+HukfEx8+H2kflB+/H+ogFSBBIGwgmCDEIPAhHC/HL/4wNTBsMKQw2zESMUoxgj/E0KzRlNJ402DUTN...

// tag::binaries-generation[]
    @ComponentBinaries
    void generateDocBinaries(ModelMap<DocumentationBinary> binaries, VariantComponentSpec component, @Path("buildDir") File buildDir) {
        binaries.create("exploded") { binary ->
            outputDir = new File(buildDir, "${component.name}/${binary.name}")
        }
    }
// end::binaries-generation[]

// tag::text-tasks-generation[]
    @BinaryTasks

        then:
        result.ignoreBuildSrc.assertTasksExecuted(":compileDocsExplodedReference", ":compileDocsExplodedUserguide", ":docsExploded", ":assemble")

        and:
        languageTypeSample.dir.file("build/docs/exploded").assertHasDescendants(
                "reference/README.txt",
                "userguide/chapter1.html",
                "userguide/chapter2.html",
                "userguide/index.html")
    }

This is because, as described in <<build_cache_concepts.adoc#concepts_repeatable_task_outputs,repeatable task outputs>>, rebuilding an archive often changes the metadata in the archive.
You can depend on the exploded contents of the archive instead.
See also the section on dealing with <<common_caching_problems.adoc#volatile_outputs,non-repeatable outputs>>.

=== Dealing with file paths

Vadim Rutkovsky <******@****.***> 1671109648 +0100

 | `application/x-xz`       |

All files with these extensions and mime types are excluded from compression,
even if compression is enabled for all types.

## To test the setup

To test this setup, practice put calls to the server using `mc` and use `mc ls` on
the data directory to view the size of the object.

## Explore Further

- [Use `mc` with MinIO Server](https://min.io/docs/minio/linux/reference/minio-mc.html)

        def spec = Mock(Spec)
        def included = Stub(FileVisitDetails)
        def excluded = Stub(FileVisitDetails)
        def visitor = Mock(FileVisitor)

        when:
        tree.visit(visitor)

        then:
        _ * patterns.asSpec >> spec
        1 * spec.isSatisfiedBy(included) >> true
        1 * spec.isSatisfiedBy(excluded) >> false
        1 * source.visit(_) >> { FileVisitor nestedVisitor ->

        0 * _

        and:
        !filter.isSatisfiedBy(excluded)
        filter.isSatisfiedBy(notExcluded)
    }

    def "exclude filter configures only the default project when exact match on task name found when subprojects included"() {
        def excluded = Stub(Task)
        _ * excluded.name >> "b"
        _ * excluded.project >> projectModel1

func (c Clusters) Primaries(excluded ...Cluster) Clusters {
	return c.filterClusters(func(cc Cluster) bool {
		return cc.IsPrimary()
	}, exclude(excluded...))
}

// Exclude returns all clusters not given as input.
func (c Clusters) Exclude(excluded ...Cluster) Clusters {
	return c.filterClusters(func(cc Cluster) bool {
		return true
	}, exclude(excluded...))
}

 * Within a process, only one thread is allowed write access to a given expanded directory. This is to avoid concurrent writes
 * to the same expanded directory.
 *
 * Multiple threads are allowed to extract into different expanded directories concurrently.
 * <p>
 * There currently are no checks on modifications to files in the expanded directory. This can cause problems if the expanded directory is used