Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default to Java17-based builder-images for native executable generation #26319

Merged

Commits on Jun 23, 2022

  1. Revert "Select Java17 builder image for native when project build wit…

    …h Java 17"
    
    This reverts commit e2771de and makes
    the use of java17-based builder-images the default without taking into
    account the JVM version used to build the project.
    
    The motivation for this change is that the builder-image compiles
    bytecode to binary files and in theory a Java17-based builder-image
    should be able to compile Java bytecode generated by a Java11 compiler
    and produce a native executable that behaves the same as a native
    executable generated by a Java11-based builder-image.
    
    A key difference between a native executable generated by a Java11-based
    builder-image and a native executable generated by a Java17-based
    builder-image is that they include (embedded in the native executable)
    different implementations of the JDK standard libraries. In theory this
    should not be an issue, given that Java is backwards compatible and the
    Java11 APIs of the standard libraries should still be implemented and
    respected in Java17.
    
    This change will allow us to test this hypothesis in practice as well :)
    If things work as expected then we can drop Java11-based builder-images
    and only generate/maintain Java17-based ones.
    zakkak committed Jun 23, 2022
    Configuration menu
    Copy the full SHA
    7999502 View commit details
    Browse the repository at this point in the history