Александър Куртаков
Александър Куртаков
Is there any progress on this one?
As long as the person merging/contributing plans to work on these new failures in the short term it should be fine as having huge PRs is also not nice for...
Getting rid of legacy mistakes is very lengthy process and most of the time it is not straightforward find and replace but requires some rearrangement of the code to make...
This has conflicts with master now. I'm closing it and will prepare a separate PR to fix these.
> I would also use Path for new code, but is it worth to enlarge the git history with rewriting it? As the PR is not just about that and...
Would you please give exact instructions and maybe sample plugin to reproduce the issue?
As this is tests code it's fine to bump its BREE to 21 and land this one in. We already struggle with maintaining the PR queue so better to not...
I don't mind moving to Java 21 but mass moves tend to make things go unnoticed (e.g. many new warnings at once) .
Another thing to consider is that moving tests to Java 21 makes it harder to test bundles against Java 17 if the bundle under test is still on Java 17.
Is this issue still relevant?