Build change itself looks good to me. I think this solves the problem for the time being, even if the cleanup is not as complete.
For JDK 12, we should see if we can go further. /Magnus > 4 juni 2018 kl. 23:22 skrev Erik Joelsson <erik.joels...@oracle.com>: > > Given the feedback, I have revised the patch to restore the ability to > produce a legacy jre image, but it is still removed from the default > "product-images" and "images" targets. To build it you need to specify it > explicitly as "legacy-jre-image" (or mac-legacy-jre-bundle for the macosx > specific image layout). I still removed the bundle targets for the jre image > as I very much doubt anyone except Oracle was using them anyway. In addition > to this, I also updated the help text a bit to reflect these changes. > > Will this be good enough for those that still need a JRE image? > > Webrev: http://cr.openjdk.java.net/~erikj/8200132/webrev.02/index.html > > /Erik > > >> On 2018-06-01 15:02, Erik Joelsson wrote: >> Since JDK 9 and modules, the idea of a prebuilt JRE is no longer providing >> much value. The idea is rather that you link together an image with the >> modules and settings you actually need, either with or without your >> application. For this reason oracle will no longer ship JRE images that >> differ content wise to the JDK image in JDK 11 and we would like to remove >> them from the OpenJDK build to reduce complexity. >> >> Bug: https://bugs.openjdk.java.net/browse/JDK-8200132 >> >> Webrev: http://cr.openjdk.java.net/~erikj/8200132/webrev.01/ >> >> /Erik >
