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

DIRSTUDIO-1309: Upgrade to Eclipse 4.24 #43

Merged
merged 1 commit into from
Feb 16, 2024

Conversation

roubert
Copy link
Contributor

@roubert roubert commented May 14, 2023

This is an alternate version of PR #36 in case the maintainers would prefer to keep using explicit version numbers here.

All unit tests (including -Denable-ui-tests) pass. Also tested manually on an M1 Mac with macOS Ventura 13.3.1 (a).

Eclipse 4.24 is chosen because it's the newest version to which these libraries can be upgraded without having to make any other changes. Eclipse 4.25 causes a dependency error with JUnit (which eventually will need to be resolved, but isn't anything that needs to be done in order to resolve the Apple silicon issue).

@elecharny
Copy link
Contributor

Thanks, Frederick!
The pb is that we don't have a M1 or M2 based computer to test it...

If someone volunteers to tun self-hosted GitHub M1 runner, that would help

@roubert
Copy link
Contributor Author

roubert commented May 15, 2023

To get things started, maybe you could just take my word for it that this works on M1. Then you'd only need to verify that it doesn't break any of the existing platforms.

Going forward, automated testing will of course be needed to prevent accidental regressions, but that is unfortunately not something that I could help out with, but once M1 support has been added and people start using it, maybe someone else will step up and help out, when they then have an interest in keeping it working.

@elecharny
Copy link
Contributor

Hi Frederick, just merged your change! I'll check if that breaks anything on i386.
Thanks!

@roubert
Copy link
Contributor Author

roubert commented May 27, 2023

I'll check if that breaks anything on i386.

Great! How is it going, are you finding any unexpected side-effects?

@elecharny
Copy link
Contributor

@roubert Have you get Shawn McKinney mail?

@roubert
Copy link
Contributor Author

roubert commented Jun 9, 2023

@roubert Have you get Shawn McKinney mail?

Yes, thank you.

@roubert roubert changed the title DIRSTUDIO-1293: Add a native Apple silicon (aarch64) build target. DIRSTUDIO-1293: Upgrade to Eclipse 4.24 Jun 9, 2023
@roubert
Copy link
Contributor Author

roubert commented Jun 9, 2023

As I had this commit prepared, I've now updated the commit message in case you'd like to use it to update to Eclipse 4.24 (even though it now isn't needed to support Apple silicon anymore, after PR #36 was merged earlier today).

@roubert roubert changed the title DIRSTUDIO-1293: Upgrade to Eclipse 4.24 DIRSTUDIO-1309: Upgrade to Eclipse 4.24 Jul 15, 2023
@roubert
Copy link
Contributor Author

roubert commented Jul 15, 2023

I've now filed a separate ticket DIRSTUDIO-1309 specifically about updating the Eclipse platform used (unrelated to Apple silicon) and repurposed this PR for that.

@roubert
Copy link
Contributor Author

roubert commented Oct 2, 2023

The pb is that we don't have a M1 or M2 based computer to test it...

GitHub might just have solved that: https://github.blog/changelog/2023-10-02-github-actions-apple-silicon-m1-macos-runners-are-now-available-in-public-beta/

@roubert
Copy link
Contributor Author

roubert commented Feb 15, 2024

@PierreSmits, now when you're upgrading dependencies, you might want to also merge this PR.

@PierreSmits
Copy link
Member

Hi @roubert

According to my information you are a committer to this repository also. As such you can merge (valid) pull-request too.

However, I suggest to do a dummy commit to get this PR tested against latest changes in the main branch (given the age of this PR and recent upgrades).

This is the last version of Eclipse using Java 11.
@roubert
Copy link
Contributor Author

roubert commented Feb 15, 2024

Well, I'm not used to merging things like a lone ranger, without anyone else in the project first reviewing and agreeing. But I've now rebased and will force push, to trigger tests at current master.

@elecharny
Copy link
Contributor

Hi @roubert,

please go ahead ! Break things, then get them fixed - either by you are someone else -. Don't be shy :-)

@PierreSmits
Copy link
Member

Thanks @elecharny

My thoughts exactly. Our CI processes should safeguard that what gets merged in our trunk is good enough.

@PierreSmits PierreSmits self-requested a review February 16, 2024 10:56
@PierreSmits PierreSmits merged commit 97e67e1 into apache:master Feb 16, 2024
3 checks passed
@roubert roubert deleted the dirstudio-1293 branch February 18, 2024 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants