Open mlntdrv opened 1 year ago
Tycho 2.7.3 is ancient version (uses ecj 3.25.0) . As compilation is actually done by ECJ you should update to recent Tycho (4.0.4) in order to check whether the issue is fixed in newer ecj version. You may also want to try whether the code in question compiles in latest Eclipse version which would mean that ECJ is fixed.
v2.7.3 is from a year and a half ago, is it already out of support?
Only latest major stream is supported aka 4.x now. When 5.0.0 is out , 5.x would be the supported stream.
v2.7.3 is from a year and a half ago, is it already out of support?
Means 6 new releases of Eclipse compiler, nevertheless it should work to specify a never ECJ even with Tycho 2.7.3 (please be aware that there is even a 2.7.5 out), but as @akurtakov mentions it is very unlikely that if there is a problem we can analyze and fix it see https://github.com/eclipse-tycho/tycho/blob/master/CONTRIBUTING.md#backporting especially if it is a compiler bug.
Thank you for your responses, guys.
it should work to specify a never ECJ even with Tycho 2.7.3 (please be aware that there is even a 2.7.5 out)
I've tried with 2.7.5, same (both 2.7.3 and 2.7.5 use ecj-3.29.0 BTW). How can I change the ECJ version for tycho-2.7.5? I use the following plugins: tycho-maven-plugin target-platform-configuration tycho-p2-repository-plugin tycho-p2-director-plugin
Code:
There is a
Supplier
that's been fed toOptional#or
, which returns anotherOptional
, so definitely not an empty lambda, butSupplier<Optional<List<Something>>>
instead.