The jextract image we publish is essentially just a runtime image produced by jlink with a launcher script in the bin folder. The launcher script just runs the java launcher located in the same directory.
The issue is that, adding the jextract bin directory to the path (to run jextract) also adds the java launcher, which will then interfere with other java versions on the path.
We can improve this situation by changing the layout of the jextract image we create to put the launcher script in a separate folder from the launcher itself.
The issue is that, adding the jextract bin directory to the path (to run jextract) also adds the java launcher, which will then interfere with other java versions on the path.
We can improve this situation by changing the layout of the jextract image we create to put the launcher script in a separate folder from the launcher itself.