> On 17 May 2023, at 23:01, Gregg Wonderly <gregg...@cox.net> wrote: > > Again, the supposition here, is that somehow anyone who once built an > application into a jar file that is in use today, can somehow cause a release > of a new version of the JDK that appears in a user’s environment, to > correlate with getting a new, compatible version of the application
Not only is this — controlling the runtime environment and its interaction with the application — exactly what the JDK has allowed standalone applications to do since JDK 9, but also what we’ve encouraged them to do. > There really needs to be a way that the Java version for an application can > be specifically designated and that version discovered and made available to > the user through a reasonably informative mechanism. Are you not aware that this was addressed nearly five years ago? Actually, Java does better than this. It no longer requires you to depend in any way on some separately installed Java runtime on the user’s machine. The user need not even be aware that the application is written in Java. — Ron
