MacOS 14.3 M2: RCP application blank screen with Temurin 17.0.10 #1012

ivy-lli · 2024-01-29T09:21:30Z

Describe the bug
Since the update to Temurin 17.0.10 (from Temurin 17.0.9), my started Eclipse RCP application shows only an empty screen.

To Reproduce

Install Eclipse RCP 2023-12 (4.30.0) https://www.eclipse.org/downloads/packages/release/2023-12/r/eclipse-ide-rcp-and-rap-developers
Create a new RCP application, done as described here: https://www.vogella.com/tutorials/EclipseRCP/article.html#generatetemplatewithcontent
Add Temurin 17.0.10 to Eclipse
- Open Preferences
- Java > Installed JREs
- Add...
- Select it
- Apply
Start the Eclipse application as described in the tutorial (Step 2)
-> Empty application
Close the Eclipse application
Add Temurin 17.0.9 to Eclipse
- Same as step 3
Make sure the Eclipse application uses Temurin 17.0.9
- Run
- Run configurations...
- Choose our Eclipse Application
- Java Runtime Environment
- Runtime JRE: select Temurin 17.0.9
- Apply
Start the Eclipse application
-> Application with sample content

I can also provide the workspace via a GitHub repo, but it is not more than the wizard for new RCP Applications created.

Expected behavior
The Eclipse RCP application should also show the sample content

Screenshots
Temurin 17.0.10:

Temurin 17.0.9:

Environment:

Select the platform(s) on which the behavior is seen:

- All OS
- Windows
- Linux
- macOS

Additional OS info (e.g. OS version, Linux Desktop, etc)
OS: MacOS Sonoma 14.3
Platform: MacBook Pro M2, 2023
JRE/JDK version
Temurin 17.0.10:

openjdk version "17.0.10" 2024-01-16 
OpenJDK Runtime Environment Temurin-17.0.10+7 (build 17.0.10+7) 
OpenJDK 64-Bit Server VM Temurin-17.0.10+7 (build 17.0.10+7, mixed mode)

Temurin 17.0.9:

openjdk version "17.0.9" 2023-10-17
OpenJDK Runtime Environment Temurin-17.0.9+9 (build 17.0.9+9)
OpenJDK 64-Bit Server VM Temurin-17.0.9+9 (build 17.0.9+9, mixed mode)

Version since
Tested with 4.30

Workaround (or) Additional context
I didn't see any log, crash, or something like that.
I also already opened an issue at the Temurin site: adoptium/adoptium-support#1008

The text was updated successfully, but these errors were encountered:

iloveeclipse · 2024-01-29T09:23:36Z

Could you please try with latest 4.31 nightly build?

ivy-lli · 2024-01-29T09:26:39Z

One addition

I quickly wanted to see if this bug is also the case if I use the shipped JDK just j in version 17.0.10.
As the Eclipse 4.30 is shipped with the latest JDK v21, I installed the JustJ laster 17 package via the software manager, which then removed the v21 and installed the v17.0.10. After the installation, I restarted Eclipse as said, and now it is not starting at all:

I'm not sure if it has to do with the same problem, but now I have a log file:
1706519978372.log

I just wanted to mention it, but as said, maybe it has nothing to do with the bug of this issue.

ivy-lli · 2024-01-29T09:38:22Z

Tried it with Version: 2024-03 M1 (4.31.0 M1) / Build id: 20240111-1612

Same problem, with Temurin 17.0.10 the screen in blank, with Temurin 17.0.9 everything seems to work as expected.

merks · 2024-01-29T09:42:59Z

Note that this works on Windows:

Are there any clues in the console?

HeikoKlare · 2024-01-29T09:44:41Z

I just tried with yesterday's I-Build artifacts started from current sources:
Version: 2024-03 (4.31)
Build id: I20240128-1800

Plain SWT applications work fine:

Log is empty.

ivy-lli · 2024-01-29T09:50:05Z

I just tried with yesterday's I-Build artifacts started from current sources: Version: 2024-03 (4.31) Build id: I20240128-1800

Yes exaclty the first image I've got with our real RCP application, I just wanted to create an issue on a simple reproducable way, what is the reason why I tried it with a base RCP application too.

I started once again and now I've got a log, but not sure if this has something to do with it, maybe it is also because of some config changes...

eclipse_rcp-startup.log

ivy-lli · 2024-01-29T09:51:46Z

I think it also works with Linux (latest linux mint 21.3). I have an internal coworker which shortly tried our application with Temurin 17.0.10 at it seems to work fine.

Phillipus · 2024-01-29T09:54:37Z

I can confirm this. Launching a child Eclipse or an RCP app with Temurin JDK 17.0.10+7 leads to a totally blank app.

MacBook M2
Sonoma 14.3

merks · 2024-01-29T10:02:34Z

The log just makes it sound like some bundle was not included in the launch configuration. It looks like the leaf cause is this failure:

Unresolved requirement: Import-Package: org.apache.commons.io; version="[1.4.0,2.0.0)"

But how that's related to the JRE version is entirely unclear.

Could you maybe try to add the bundle explicitly?

HeikoKlare · 2024-01-29T10:04:46Z

Note that my screenshot with an empty RCP application is taken without any log errors. After switching back to Temurin 17.0.9 with the exact same workspace setup, the application looks good.

Phillipus · 2024-01-29T10:05:55Z

Note that my screenshot with an empty RCP application is taken without any log errors. After switching back to Temurin 17.0.9 with the exact same workspace setup, the application looks good.

Same here. I'm using vanilla Eclipse SDK from here.

merks · 2024-01-29T10:31:14Z

So one very strange thing here is that Eclipse itself works fine, just not an RCP application. There is no clue or theory for how that is possible, and I can't reproduce it because I'm on Windows so I cannot help in this regard. 😱

ivy-lli · 2024-01-29T10:34:03Z

The log just makes it sound like some bundle was not included in the launch configuration. It looks like the leaf cause is this failure:
Unresolved requirement: Import-Package: org.apache.commons.io; version="[1.4.0,2.0.0)"
But how that's related to the JRE version is entirely unclear.

Could you maybe try to add the bundle explicitly?

Makes no difference:

Phillipus · 2024-01-29T10:35:58Z

Tested on macOS Ventura and it's OK. So seems to be a combination of:

macOS Sonoma
Temurin JDK 17.0.10+7
Launching child Eclipse/RCP app

Plain SWT Snippets are OK and work as expected when launched from Eclipse.

Phillipus · 2024-01-29T11:07:10Z

Same problem with Temurin 21.0.2+13 (but OK with 21.0.1+12).

iloveeclipse · 2024-01-29T11:09:01Z

Is that something related to "signing" of the app, may be some old signing algorithms / keys etc were revoked in new JVM's?

Phillipus · 2024-01-29T11:12:02Z

Is that something related to "signing" of the app, may be some old signing algorithms / keys etc were revoked in new JVM's?

I don't think so. These JDKs work fine if you use them to run Eclipse or an RCP app directly. The problem is when launching a child Eclipse / RCP app from Eclipse to run/debug it. The menus are rendered but not the app's contents.

Phillipus · 2024-01-29T11:33:12Z

I don't know how we can proceed to solve this one.

The situation as it stands means that if someone is running macOS Sonoma and has one of these versions of the Temurin JDK installed (currently 17.0.10+7 and 21.0.2+13) they will be able to run Eclipse OK but they will not be able to debug launch a working child instance of Eclipse or an RCP application.

FWIW simple steps to reproduce (on macOS Sonoma):

Install Temurin JDK 17.0.10+7 or 21.0.2+13
Install vanilla Eclipse SDK for macOS here
Add Temurin JDK to Eclipse from Eclipse's Settings - Java -> Installed JREs - Add
Create a new Debug Launch Configuration of product org.eclipse.sdk and Runtime JRE of the Temurin JDK
Launch child Eclipse from this configuration

merks · 2024-01-29T11:50:28Z

FYI, to reproduce using the installer one can install anything with 17.0.10 or 21.0.2 which will also use that as the JRE in that installed IDE:

It just seems bizarre that the IDE itself works (does it?) yet something is failing in the launched application (but not in SWT snippets), and nothing is in the log as an indicator...

I assume the failure is in any launch, not just a debug launch but also a run launch?

Phillipus · 2024-01-29T11:52:31Z

It just seems bizarre that the IDE itself works (does it?) yet something is failing in the launched application (but not in SWT snippets), and nothing is in the log as an indicator...

Yes the IDE itself works. Problem is only the launched app. SWT Snippets are OK too.

I assume the failure is in any launch, not just a debug launch but also a run launch?

Yep, I tried that.

iloveeclipse · 2024-01-29T11:59:01Z

I don't know how we can proceed to solve this one.

Divide and conquer.

Possible issues could be in

e4 css code (the one that renders seem not work)
SWT Mac code (the one that draws)
PDE code (the one that prepares target/ dependencies before start)
Equinox code (the one that resolves dependencies at runtime)
Platform runtime code (may be some exceptions are swallowed)
JVM code (some weird security fix that breaks rendering by not running some "dangerous" part of the code)
Btw, there was earlier a fix in JVM that introduced some stack limits for xml parsing - so if now the stack is longer, we may hit that limit. Try to start with -Djdk.xml.xpathExprGrpLimit=0 -Djdk.xml.xpathExprOpLimit=0 -Djdk.xml.xpathTotalOpLimit=0
whatever else

So one should try to reduce the problem to smallest possible example and see which partis responsible here.

Reduce to simplest possible example code and debug that part that causes example to not render
Disable css by disabling themes support in Eclipse
Start with the JVM arguments I've given above
Check JDK fixed bugs for a good candidate (similar to xpath above)
Debug with breakpoint created on "Exception" that might be swallowed
Profile with Yourkit or ny other profiler and check for exceptions / problems reported there
Enable tracing, etc

Since I don't have Mac, I can't help further ...

merks · 2024-01-29T12:02:00Z

I'm not sure how on mac java is launched. I think it uses some library in the JDK/JRE rather than like the way java executable is used directly for a launched application:

So I guess there is no good way to compare how launched processes might be different...

I wish I could help more effectively. 😢

Phillipus · 2024-01-29T12:17:23Z

When Eclipse or an RCP app is run from desktop it runs from the launcher binary file (Eclipse.app/Contents/MacOS/eclipse).

On Mac, a child Eclipse launches using the java binary. We can see that in the launch config dialog "Command Line".

The latest Mac Eclipse launcher binary is built using Mac SDK 13 while these versions of Temurin are built using Mac SDK 14. (You can determine this with the command vtool -show /path/to/binary will show this.)

I think this is the problem.

We can rule out the Eclipse IDE by copying the launch config's command line and editing it to get rid of extra stuff. For me:

/Users/phillipus/Desktop/jdk-17.0.10+7/Contents/Home/bin/java \
-XstartOnFirstThread \
-classpath /Users/phillipus/projekts/archi/workspace/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.equinox.launcher_1.6.400.v20210924-0641.jar org.eclipse.equinox.launcher.Main \
-product org.eclipse.sdk.ide \
-data /Users/phillipus/projekts/archi/workspace/../runtime-New_configuration \
-configuration file:/Users/phillipus/projekts/archi/workspace/.metadata/.plugins/org.eclipse.pde.core/New_configuration/ \
-consoleLog

Running the above in Terminal give a blank Eclipse window.

HeikoKlare · 2024-01-29T12:26:18Z

e4 css code (the one that renders seem not work)

One thing that would support this is that actually everything seems to "exist", but is simply not rendered correctly. You can see that the cursor changes on buttons, you can click buttons, open context menus etc. For example, you can open another dialog:

Btw, there was earlier a fix in JVM that introduced some stack limits for xml parsing - so if now the stack is longer, we may hit that limit. Try to start with -Djdk.xml.xpathExprGrpLimit=0 -Djdk.xml.xpathExprOpLimit=0 -Djdk.xml.xpathTotalOpLimit=0

I've tried these options, but they did not change anything.

Unfortunately I can currently not invest much into investigating this issue, since I work on Windows and only have Mac for SWT/Platform UI validation tasks.

Phillipus · 2024-01-29T12:35:34Z

The latest Mac Eclipse launcher binary is built using Mac SDK 13 while these versions of Temurin are built using Mac SDK 14. (You can determine this with the command vtool -show /path/to/binary will show this.)

The current Eclipse launcher binary is built using macOS SDK 13 (vtool -show Eclipse.app/Contents/MacOS/eclipse will show this). It might be that if ever it is built using SDK 14 we will see the same problem.

Phillipus · 2024-01-29T12:40:03Z

We can rule out e4 css code because I set up child Eclipse to not use themes and same problem.

Phillipus · 2024-01-29T12:49:17Z

From further testing I'm pretty certain the difference is because the java binary has been built using macOS SDK 14. Why this causes the problem in SWT I don't know.

I replaced just the java binary file with one from an earlier Temurin SDK and it is working OK. This supports my theory.

Phillipus · 2024-01-29T13:36:45Z

OK, I'm going to summarise the situation based on the assumption that the problem is arising because of Temurin using macOS SDK 14 to create the java binary.

This problem only manifests on macOS Sonoma (14). It's OK on Ventura (13).
It only manifests on launching a child Eclipse or RCP instance because that is launched with the java binary in the command line
It does not manifest when launching native Eclipse because that is launched with the eclipse launcher executable which has been created using an earlier macOS SDK
Why this change of SDK should cause the problem in SWT/Equinox/Whatever is unknown
Today this means that Mac developers cannot target the latest Temurin JDK if they want to debug Eclipse or RCP apps
If ever the Eclipse Mac launcher is built using macOS SDK 14 the same problem will occur when launching native Eclipse and Eclipse will be unusable on Mac Sonoma with the latest JDK

Worthy of investigation is why SWT Snippets are running OK.

Phillipus · 2024-01-29T14:08:53Z

@SyntevoAlex and @tmssngr I wonder if you could help to test something? The SmartGit app uses its own launcher binary (SmartGit) which has been built against SDK 11.3 (vtool -show SmartGit will show this). Is it possible for you to create this binary file using macOS SDK 14 and launch SmartGit with this?

- Add a new selector setClipsToBounds - Set this selector to true in Widget#drawRect - See #1012

Phillipus · 2024-03-12T10:14:42Z

This seems to be fixed in the latest I-Build after PR #1081 was merged

I also tested the latest I-Build on aarch64 by replacing the eclipse launcher binary in the Eclipse.app/Contents/MacOS directory with the one built with SDK 14 and the fix works in that case, too.

If anyone is able to test the latest I-Build, please do.

ivy-lli · 2024-03-12T15:23:04Z

Thanks for all of your work!

I quickly tested the snippet here: #1012 (comment)
With the I-Build: Eclipse 4.32.0 Integration Build: I20240311-1800
MacOS 14.4 M2, Temurin 17.0.10

Seems to work fine 👍

Phillipus · 2024-03-12T15:26:45Z

@ivy-lli Thanks for testing. 👍

A more realistic test is to launch a child Eclipse instance with the latest Temurin Java as target.

ivy-lli · 2024-03-13T07:31:16Z

I've also tried my initial report scenario, the example rcp:

For that I downloaded the newest Eclipse SDK and installed all addional software (as I honstely have no idea what is needed to make a rcp example runnable in a normal Eclipse SDK).
Opened the existing workspace with the example rcp application
Run the example application with the Temurin JRE 17.0.9 and 17.0.10

Result: It seems to work now again with both JRE's

17.0.9

17.0.10

merks · 2024-03-13T07:33:22Z

Thanks again for testing!

akurtakov · 2024-03-14T09:05:04Z

Should this one be closed now?

Fnux8890 · 2024-03-14T09:13:32Z

Im experiencing this on MacOS 14.3 on an Intel processor on a MacBook Pro.
Im using openJDK 17 and 21 but could try Temurin if that is a key difference.

If this is fixed what would I need to do to get that fix? 🙏

Phillipus · 2024-03-14T09:56:29Z

This issue shouldn't affect OpenJDK as their binaries are not compiled/linked to macOS 14.

what would I need to do to get that fix?

Use the latest I-builds of Eclipse or SWT.

Phillipus · 2024-05-15T12:03:06Z

This is not completely fixed.

I'm seeing blank areas when using a Tabbed Properties control:

It should look like this:

The fix applied in #1081 is not enough. If we apply it to NSView it works:

public NSView(long id) {
	super(id);
	OS.objc_msgSend(id, OS.sel_setClipsToBounds_, true);
}

But as explained in #1081 (comment) we can't add it there.

I think that unless we apply the fix in a place where it catches all cases we'll continue to see this bug re-appear.

@lshanmug Can you please advise?

- OS.objc_msgSend(id, OS.sel_setClipsToBounds_, true) needs to be applied in two more cases - See eclipse-platform#1012

Phillipus · 2024-05-15T12:51:40Z

New PR: #1232

- OS.objc_msgSend(id, OS.sel_setClipsToBounds_, true) needs to be applied in two more cases - See #1012

chrisrueger · 2024-07-17T10:08:42Z

Also seeing this with Eclipse (but scroll down, how I got it working with a lower Temurin JDK)

Version: 2024-06 (4.32.0)
Build id: 20240606-1231

and

Macbook Air M3 2024
MacOS Sonoma 14.5 (23F79)

and

OpenJDK Runtime Environment Temurin-17.0.11+9 (build 17.0.11+9) (installed via .pkg at /Library/Java/JavaVirtualMachines/temurin-17.jdk)
as well as OpenJDK Runtime Environment Temurin-21.0.3+9 (build 21.0.3+9-LTS) (installed via .pkg at /Library/Java/JavaVirtualMachines/temurin-21.jdk)

For sake of reproduction:

trying to launch dev child eclipse instance for bndtools (https://bndtools.org/development.html)
launch bndtools.cocoa.macosx.aarch64.bndrun

But it works with JDK Temurin 17.0.9+9

I did not have this problem on my Macbook Pro M1.
There I was running JDK Temurin 17.0.9+9.

When I use this JDK Temurin 17.0.9+9 on my M3, it works 🥳

Summary:

Works with https://github.com/adoptium/temurin17-binaries/releases/tag/jdk-17.0.9%2B9 installed as extracted tar into /Users/me/Documents/development/jdks/jdk-17.0.9+9
does not work with
- OpenJDK Runtime Environment Temurin-17.0.11+9 (build 17.0.11+9) (installed via .pkg at /Library/Java/JavaVirtualMachines/temurin-17.jdk)
- as well as OpenJDK Runtime Environment Temurin-21.0.3+9 (build 21.0.3+9-LTS) (installed via .pkg at /Library/Java/JavaVirtualMachines/temurin-21.jdk)

Phillipus · 2024-07-17T10:30:52Z

@chrisrueger This should all be fixed in Eclipse 4.32. If you are still seeing a blank UI when running a child Eclipse instance then perhaps your target Eclipse SDK version is an earlier version?

chrisrueger · 2024-07-17T11:09:36Z

@chrisrueger This should all be fixed in Eclipse 4.32. If you are still seeing a blank UI when running a child Eclipse instance then perhaps your target Eclipse SDK version is an earlier version?

Yes that is the case. Bndtools so far always uses an earlier version. There is an open issue at bnd bndtools/bnd#5815

So then i think i am fine with my workaround to uses temurin 17.0.9+9 and i will talk with the bnd team about it.

Phillipus · 2024-07-17T11:16:19Z

Another alternative is to use a non-Temurin target JDK (OpenJDK, Azul, etc) that has not been built/linked linked to macOS 14 SDK.

Phillipus · 2024-07-17T11:30:06Z

Another alternative is to use a non-Temurin target JDK (OpenJDK, Azul, etc) that has not been built/linked linked to macOS 14 SDK.

To find out which macOS SDK the JDK has been linked to:

Navigate to the java binary executable (typically found in <jdk-root-folder>/Contents/Home/bin)
Open the Terminal and run this command: vtool -show java
Look for the sdk entry in the output

Temurin 17.0.11+9 gives the following output and you can see the sdk 14.0 entry which indicates that this JDK will cause problems on earlier versions of Eclipse:

Load command 10
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform MACOS
    minos 11.0
      sdk 14.0
   ntools 1
     tool LD
  version 1022.1
Load command 11
      cmd LC_SOURCE_VERSION
  cmdsize 16
  version 0.0

Azul JDK gives the following output and you can see the sdk 13.3 entry which indicates that this JDK will be OK:

Load command 10
      cmd LC_BUILD_VERSION
  cmdsize 32
 platform MACOS
    minos 11.0
      sdk 13.3
   ntools 1
     tool LD
  version 857.1
Load command 11
      cmd LC_SOURCE_VERSION
  cmdsize 16
  version 0.0

It seems we can stay on older Eclipse 4.25 but use a higher SWT version which has fixed the SWT bug (see eclipse-platform/eclipse.platform.swt#1012). Signed-off-by: Christoph Rueger <chrisrueger@gmail.com>

Phillipus mentioned this issue Jan 29, 2024

MacOS 14.3 M2: Temurin 17.0.10 has problem with starting an Eclipse RCP application adoptium/adoptium-support#1008

Closed

merks pushed a commit that referenced this issue Mar 11, 2024

Fix for Mac drawing bug issue 1012

d06d1a1

- Add a new selector setClipsToBounds - Set this selector to true in Widget#drawRect - See #1012

Phillipus mentioned this issue Mar 19, 2024

⚠️ Eclipse versioning issues archimatetool/archi#1036

Closed

merks mentioned this issue Mar 21, 2024

Blank workbench on macOS aarch64 eclipse-pde/eclipse.pde#1211

Closed

Phillipus mentioned this issue Apr 4, 2024

switching scheme in runtime workbench doesn't work eclipse-platform/eclipse.platform.ui#1790

Closed

ashitsalesforce mentioned this issue Apr 11, 2024

Problems when running on dataloader on MacOS 14.4.1 forcedotcom/dataloader#1073

Closed

himi mentioned this issue May 1, 2024

ST6RI-753 Move to Eclipse version 2024-03 Systems-Modeling/SysML-v2-Pilot-Implementation#563

Merged

Phillipus added a commit to Phillipus/eclipse.platform.swt that referenced this issue May 15, 2024

Fix for Mac drawing bug issue 1012 part 2

89889e3

- OS.objc_msgSend(id, OS.sel_setClipsToBounds_, true) needs to be applied in two more cases - See eclipse-platform#1012

Phillipus mentioned this issue May 15, 2024

Fix for Mac drawing bug issue 1012 part 2 #1232

Merged

lshanmug pushed a commit that referenced this issue May 16, 2024

Fix for Mac drawing bug issue 1012 part 2 (#1232)

a39c321

- OS.objc_msgSend(id, OS.sel_setClipsToBounds_, true) needs to be applied in two more cases - See #1012

Phillipus mentioned this issue May 16, 2024

[Mac] Proper fix for Mac blank UI - add setClipsToBounds in NSView constructor #1235

Open

AlexisDrogoul mentioned this issue Jun 4, 2024

Using Temurin 17.0.10 or 21.0.2+13 on macOS Sonoma breaks the UI of GAMA gama-platform/gama#193

Closed

chrisrueger mentioned this issue Jul 17, 2024

Issues with bndtools Eclipse dev instance on MacOS Sonoma 14.3+ with temurin JDK > 17.0.09+9 bndtools/bnd#6185

Closed

chrisrueger mentioned this issue Jul 17, 2024

upgrade SWT to 3.126 to fix MacOS / JDK bug bndtools/bnd#6186

Merged

MacOS 14.3 M2: RCP application blank screen with Temurin 17.0.10 #1012

MacOS 14.3 M2: RCP application blank screen with Temurin 17.0.10 #1012

Comments

ivy-lli commented Jan 29, 2024

iloveeclipse commented Jan 29, 2024

ivy-lli commented Jan 29, 2024

ivy-lli commented Jan 29, 2024

merks commented Jan 29, 2024

HeikoKlare commented Jan 29, 2024

ivy-lli commented Jan 29, 2024

ivy-lli commented Jan 29, 2024

Phillipus commented Jan 29, 2024 • edited Loading

merks commented Jan 29, 2024

HeikoKlare commented Jan 29, 2024

Phillipus commented Jan 29, 2024

merks commented Jan 29, 2024

ivy-lli commented Jan 29, 2024

Phillipus commented Jan 29, 2024 • edited Loading

Phillipus commented Jan 29, 2024

iloveeclipse commented Jan 29, 2024

Phillipus commented Jan 29, 2024

Phillipus commented Jan 29, 2024 • edited Loading

merks commented Jan 29, 2024

Phillipus commented Jan 29, 2024

iloveeclipse commented Jan 29, 2024

merks commented Jan 29, 2024

Phillipus commented Jan 29, 2024 • edited Loading

HeikoKlare commented Jan 29, 2024

Phillipus commented Jan 29, 2024 • edited Loading

Phillipus commented Jan 29, 2024

Phillipus commented Jan 29, 2024 • edited Loading

Phillipus commented Jan 29, 2024 • edited Loading

Phillipus commented Jan 29, 2024

Phillipus commented Mar 12, 2024

ivy-lli commented Mar 12, 2024

Phillipus commented Mar 12, 2024 • edited Loading

ivy-lli commented Mar 13, 2024

merks commented Mar 13, 2024

akurtakov commented Mar 14, 2024

Fnux8890 commented Mar 14, 2024

Phillipus commented Mar 14, 2024

Phillipus commented May 15, 2024 • edited Loading

Phillipus commented May 15, 2024

chrisrueger commented Jul 17, 2024 • edited Loading

But it works with JDK Temurin 17.0.9+9

Phillipus commented Jul 17, 2024 • edited Loading

chrisrueger commented Jul 17, 2024

Phillipus commented Jul 17, 2024 • edited Loading

Phillipus commented Jul 17, 2024

Phillipus commented Jan 29, 2024 •

edited

Loading

Phillipus commented Jan 29, 2024 •

edited

Loading

Phillipus commented Jan 29, 2024 •

edited

Loading

Phillipus commented Jan 29, 2024 •

edited

Loading

Phillipus commented Jan 29, 2024 •

edited

Loading

Phillipus commented Jan 29, 2024 •

edited

Loading

Phillipus commented Jan 29, 2024 •

edited

Loading

Phillipus commented Mar 12, 2024 •

edited

Loading

Phillipus commented May 15, 2024 •

edited

Loading

chrisrueger commented Jul 17, 2024 •

edited

Loading

Phillipus commented Jul 17, 2024 •

edited

Loading

Phillipus commented Jul 17, 2024 •

edited

Loading