On Tue, 6 Jan 2026 20:11:16 GMT, Andy Goryachev <[email protected]> wrote:
>> Yeah, it is just a difference of opinion in the ECJ compiler and javac. It >> can probably be written slightly differently so it compiles properly under >> both. >> >> Also, I did fix a lot of those, but that PR died. Fixing ParsedValue >> however is IMHO a waste; that thing should never have had generic arguments >> in the first place; it is a classic example where adding generics costs more >> than it benefits. > > yeah. it just bothers me that before it was quietly ignored and now any time > I touch the file it gives me a bunch of errors. we could complain to Eclipse > folks or just fix it ourselves... Yeah, often though the answer will be that it confirms to the specification, and that the specification is not tight enough in some areas, resulting in slight differences between ecj/javac. I've seen it a bunch of times (often when I join a large project that has been developed exclusively in IntelliJ for a while, which only uses javac) but there's always an easy work around. I can take a look; if I can isolate the issue, I may even file a bug report for the compiler. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/1990#discussion_r2666170134
