I work on a product that is built from a collection of plugins. Many of the plugins are distributed after the main framework is installed. That product will always need a full JRE because there is no way to know in advance which modules will be needed.
A full JRE “image” is a requirement for me. Also, jlink apparently only works with 100% modular applications. That will be impossible in the near term as all dependencies are not yet modularized and they may never be. Modularization has been very disruptive. We have yet to move past Java 8 because code doesn’t “just work” when transitioning from Java 8 to anything beyond. With previous upgrades we only had to deal with minor issues, if any. Scott > On Jun 2, 2018, at 3:05 AM, Aleksey Shipilev <sh...@redhat.com> wrote: > > Therefore, I believe removing jre is too disruptive, at least for 11, at > least until we see that the > whole jlink/jimage thing really works out in the wider Java ecosystem and > JREs are really abandoned. > > Thanks, > -Aleksey >
