Proposed functional slice breakdown

[vpa1977]

Split slices into

• core : minimal set of files required for running java 8
• security: required for encryption and tls tasks
• devel: debugging, profiling and instrumentation
• awt: graphics tasks
• tools: tools laucher

This allows to build chiselled jre based on the functions required:

RUN mkdir -p /rootfs \
      && chisel cut --release /opt/chisel-releases --root /rootfs \
     openjdk-8-jre-headless_core  \
     openjdk-8-jre-headless_security  \
    base-files_bin \

will build something that can curl github over https.

RUN mkdir -p /rootfs \
      && chisel cut --release /opt/chisel-releases --root /rootfs \
     openjdk-8-jre-headless_core  \
     openjdk-8-jre-headless_security  \
     openjdk-8-jre-headless_management \
    base-files_bin \

host a minecraft server

RUN mkdir -p /rootfs \
      && chisel cut --release /opt/chisel-releases --root /rootfs \
     openjdk-8-jre-headless_core  \
     openjdk-8-jre-headless_security  \
     openjdk-8-jre-headless_awt \
    base-files_bin \

manipulate pdf files

etc.

[vpa1977]

• lets split devel slice into jfr / debugging|profiling
• split out ext slice from core
• comment on core that we should not take away dependencies since rt.jar is there

[cjdcordeiro]

Thanks @vpa1977 ! This is looking great. I confirm that this is the right approach (slicing with basis on the functional unit).

I've left a few comments and suggestions for changes, but after that, we should be good to merge it ;)

[vpa1977]

I've added draft rockcrafters/chiselled-jre#107 for the chiselled jre so that we could validate this pull request against chiselled jre repo

[cjdcordeiro]

thanks for this @vpa1977

i'll merge it and do some changes.