Open cpovirk opened 1 month ago
Thanks for the report.
I'm surprised by the first issue (Dagger 2.50 - 2.51) since we do have a check that all of the Dagger-specific class files are compatible with JDK 8 here.
However, I'm not surprised by the second issue because the check does not validate Dagger's shaded class files (which it probably should), and the shaded XProcessing dependency has been increasing its target JDK requirements quite aggressively (I think it's JDK 11 currently).
Either way, I can update the release notes to mention these changes.
The check definitely looks to be validating the class-file version (so it would catch the XProcessing problem if not for the caveat you mentioned), but perhaps it's not validating usage of APIs from newer versions of Java (which are still possible even with older class files). For the latter, you could try building with --release 8
(or whatever version you now want as your baseline :)) or using Animal Sniffer. That may or may not turn into a yak shave :) Thanks for having a look at the release notes.
In my testing with Caliper, I can build under JDK 8 with Dagger 2.50 but not with 2.51:
Additionally, somewhere after 2.51 but by 2.56, I start seeing this failure even earlier:
No one seems to have minded in the past year, so that's good news :)