-
-
Notifications
You must be signed in to change notification settings - Fork 301
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
Issues with bndtools Eclipse dev instance on MacOS Sonoma 14.3+ with temurin JDK > 17.0.09+9 #6185
Comments
@pkriens @bjhargrave @kriegfrj I was wondering how this was done. Any docu links? Furthermore: in #5815 @peterkir was mentioned, that who is working on some contributions (I guess this refers to the Oomph templates). @peterkir could you share your thoughts on that issue? Basically what I am asking is: |
Yes, I did the hand crafting. I don't have any docs on what I did. It happens so infrequently, I had no confidence what I did for 4.25 would even apply to any future eclipse release. |
Thanks @bjhargrave In the meantime I took a shot in the dark and just upgraded Eclipse SWT to the latest version (from 3.121 to 3.126) and I suddenly everything looks fine again. |
Wasn't @kriegfrj also intending to something with an update for this? |
Based on eclipse-platform/eclipse.platform.swt#1012 (comment) and comments below.
The problem: new contributors will have a hard time figuring out what's wrong because the dev child eclipse instance shows a broken Ui without buttons etc.
This happens under the following setup:
and any Eclipse Temurin JDK > 17.0.09+9 such as:
Then, when launching bndtools Eclipse dev instance via
bndtools.cocoa.macosx.aarch64.bndrun
it looks like this:Workarounds
Relates to #5815
The text was updated successfully, but these errors were encountered: