On Sun, Jun 2, 2019 at 5:48 PM Roland Grunberg <rgrun...@redhat.com> wrote:
> On Sunday, June 2, 2019, Matthias Sohn <matthias.s...@gmail.com> 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. > Meanwhile I found that the build failure of https://git.eclipse.org/r/#/c/143168/ updating EGit to use this version of bouncycastle is caused by this issue. The I-Build https://download.eclipse.org/tools/orbit/downloads/drops/I20190602181010/ which contains the fix https://git.eclipse.org/r/#/c/143182/ fixes this issue. Also Alexander confirmed in https://bugs.eclipse.org/bugs/show_bug.cgi?id=547570 that this fix now enables Eclipse Passage to update to bouncycastle 1.61 which didn't work with the earlier R-build. -Matthias
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
