Have a separate layers for SNAPSHOT dependencies

[FrogDevelopper]

Feature description

As explained in How are Jib applications layered?, we could have a separated layer for the "SNAPSHOT" dependencies from the other so to not update the "static" dependencies layer that does not change between 2 builds

I've been able to do it locally by overloading the BuildLayersTask task

    withType<BuildLayersTask> {
        doLast {
            // moving SNAPSHOT into a different layer
            copy {
                from(outputDir.dir("libs"))
                    .include("*-SNAPSHOT.jar")
                    .into(outputDir.dir("snapshotsLibs"))
            }
            delete {
                delete(fileTree(outputDir.dir("libs")).matching {
                    include("*-SNAPSHOT.jar")
                })
            }
        }
    }

    withType<MicronautDockerfile> {
        copyFile("layers/snapshotsLibs", "/home/app/libs")
}

but I feel that would be a great feature to be included by default

[melix]

I am working on something like this, which would actually make the difference between:

• external dependencies
• external dependencies with SNAPSHOT
• project dependencies (e.g in a multiproject build)
• application

And making use of COPY --link to make things even faster.