Александър Куртаков
Александър Куртаков
@deepika-u The source of truth for that should be https://github.com/eclipse-platform/eclipse.platform.swt/blob/master/CODEOWNERS . If someone doesn't feel like being bugged too much with that, being inactive, etc. - that path is like...
@BeckerWdf I really have no idea which information you would like to be in which document so please add it wherever you see relevant.
After more than a year I'm closing this issue as it's really non-actionable. It's best if whoever is still active to spend time on PRs.
For the record - Perf tests results (at least as far as I'm aware) have only be produced by the project on Linux. I was never involved nor remember anything...
Unfortunately, I have found any timing in VMs to be totally unreliable. Sometimes VMs just "sleep" for extended periods and next time they "wakeup" the wallclock is already above any...
> Here, the test takes 28 minutes, how unreliable should VM be to skip half an hour? If it's github runner - it might have been affected by the degraded...
Do you think you can spend the time to provide a PR?
@deepika-u If one uses JDT's Java editor the behavior is as I described but I I agree that it's a very fine line where exactly the bug lies without further...
It's most likely a Generic Editor issue aka Platform UI.
I would strongly recommend going for https://openjdk.org/jeps/442 (Java 21 requirement) as jnr-ffi is not fun with Mac OS signing and the whole Orbit fuzz (https://github.com/eclipse-orbit/orbit-simrel/blob/6926eeed8ffaf2174b0fd42bc3c4e94208bda216/maven-sign/tp/MavenSign.target#L6)