macOS exported app fails with `JRExLoadFullError`

[SableRaf]

Description

A user reported on Reddit that exported applications from Processing 4 fail to launch on macOS, showing a JRExLoadFullError or JRELoadError popup.

Edit: Exporting on macOS may also throw error java.util.NoSuchElementException: No value present. See #1193

Cause

The export logic in JavaBuild.java looks for a directory that starts with jdk-, but in our current setup, the embedded JDK starts with jdk (without the dash). This causes the path resolution to fail, and no JRE is bundled, leading to the JRExLoadFullError.

Screenshots

[challah]

@SableRaf I'd like to take this on. Is this just about removing the dash in jdk- to jdk? If so, please assign me this issue. Thank you.

[SableRaf]

Thanks Jordanne. Good to see you here! I have assigned the issue to you. Feel free to open a Pull Request and we'll be happy to review it. Let me know if you need any guidance 😃

[challah]

It looks like there's an issue beyond the jdk-/jdk directory path issue for the exports. @Stefterv can you look into this please? Thanks.

Image attached with the .filter(p -> p.getFileName().toString().startsWith("jdk")) change and trying to open an exported app.

[Stefterv]

Just looked into it a bit deeper right now and seems like the launch4j specifically expects an original JDK and not the stripped down version we're shipping to work. This indeed goes a little deeper than I first expected so I'll assign it to myself