add common-service dependency layer about dockerprepareplugin HOT 5 CLOSED

Works perfectly, thank you!

from dockerprepareplugin.

I'm thinking of adding a build.gradle setting that might look like this:

dockerprepare {
  commonService 'spring-boot-starter-web'
}

spring-boot-starter-web has 21 transitive dependencies. During a build, all 21 resolved jar files would be copied into the first layer, giving us 3 layers:

L1: spring-boot-starter-web
L2: all other dependent jar files
L3: everything else, i.e. src/main/**

from dockerprepareplugin.

That would be an awesome feature.

If the commonService could be configured to be a project dependency that would essentially allow to tuck away in L1 layer many other 3rd parties (we have protobuf/gRPC, vavr, Guava, resilience4j and Ignite to name a few). Multi-project Gradle configuration would definitely benefit from that.

One could make the case that looking at inter-project dependencies, the dependency tree (just between the different projects) outlines the optimal reusable layer structure.

from dockerprepareplugin.

ok, This is implemented now. I changed the syntax a little to allow for multiple dependencies in the commonService layer:

dockerprepare{
    commonService ['org.springframework.boot:spring-boot-starter-web','org.springframework.boot:spring-boot-starter-actuator']
}

from dockerprepareplugin.

fixed in this version:

plugins {
id "com.garyclayburg.dockerprepare" version "1.1.0"
}

from dockerprepareplugin.