exploded-war-child-copy-spec-example.png...

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

            task explodedZip(type: Copy) {
                into 'build/exploded'
                with zip
            }
            task copyFromRootSpec(type: Copy) {
                into 'build/copy'
                with zip.rootSpec
            }
        '''
        when:
        run 'explodedZip', 'copyFromRootSpec'
        then:
        file('build/exploded').assertHasDescendants(

        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

- An absolute path to the input artifact or in the input artifact (for an input directory).
- A relative path.

Gradle uses the absolute path as the location of the output artifact.
For example, if the input artifact is an exploded WAR, then the transform action can call `TransformOutputs.file()` for all jar files in the `WEB-INF/lib` directory.
The output of the transform would then be the library JARs of the web application.

Sometimes, this is what you want, but not always.
Consider the following example that copies files into a directory structure that a Java Servlet container can use to deliver a website:

image::exploded-war-child-copy-spec-example.png[]

This is not a straightforward copy as the `WEB-INF` directory and its subdirectories don't exist within the project, so they must be created during the copy.

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)