Hello. Is it possible to do a lazy artifact transform? What I actually mean: there is a JAR dependency from remote repository that needs to be unpacked in a task. The problem is that it's eagerly resolved during

CONFIGURING

phase, not

EXECUTING

like e.g. regular compilation dependency. The problem is that the artifact is quite big and it's resolved in a single-thread CONFIGURING phase (while potentially it could be multi-thread EXECUTING). I tried this approach:

configurations {
    remoteApp {
        attributes {
            attribute(ArtifactTypeDefinition.ARTIFACT_TYPE_ATTRIBUTE, "unzipped")
        }
    }
}

dependencies {
    // example from <https://docs.gradle.org/current/userguide/artifact_transforms.html#artifact_transforms_without_parameters>
    // public abstract class Unzip implements TransformAction<TransformParameters.None> {
    registerTransform(Unzip) {
        from.attribute(ArtifactTypeDefinition.ARTIFACT_TYPE_ATTRIBUTE, "jar")
        to.attribute(ArtifactTypeDefinition.ARTIFACT_TYPE_ATTRIBUTE, "unzipped")
    }

    // libs is toml version catalog
    remoteApp libs.remoteApp
}

def unpackRemoteAppTask = tasks.register('unpackRemoteApp', Copy.class) {
    from({ configurations.remoteApp })
    into layout.buildDirectory.dir("remoteapp/x86")
    fileMode = 0755
    dirMode = 0755
}

The artifact transform is done when you request the artifacts, so it already is as lazy as possible. If you request the files at configuration phase, Gradle has no other choice than executing the transform.

You are right! Thanks, that's a good point. Without the configuration cache it behaves as expected.