On Sunday, June 2, 2019, Matthias Sohn <[email protected]> wrote: > > > I agree this looks inconsistent. No clue why this happened, comparing the > sources against 1.60 > didn't reveal the reason why the build decided for JavaSE 9. I pushed a > fix for review > https://git.eclipse.org/r/#/c/143182/ >
I haven't looked too deeply yet but my guess is that the metadata generation detects a module-info file and treats this as requiring Java 9 at a minimum. The affected property can be manually set as needed though. Given that the scope is limited, we can do an RC2a. I would just make sure to test to confirm it works as you expect.
_______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
