Closed dmatej closed 3 years ago
All commits are signed, but eclipsefdn/eca has different opinion - what can I do?
I agree, it does appear you have signed all the commits and you do have a valid ECA. A committer can go ahead and merge, once a review has been completed.
All commits are signed, but eclipsefdn/eca has different opinion - what can I do?
I tried even to match my name including czech letters č and ě, but it is still the same. I'm giving up fighting with the eclipsefdn/eca checker ... the PR is prepared to be merged now, I don't plan any other pushes except those which would come from reviews.
I rebased the PR, the build will now fail here for two reasons:
npn is not released yet
I reenabled AlpnSupportTest, locally tested in following configurations (see npn/openjsse profiles, default is no profile -> using JDK's impl). Travis is using now obsoleted JDK8u151 which does not contain backported ALPN support from newer JDKs yet.
OpenJDK 8u275, openjsse 1.1.5 ... SUCCESS
OpenJDK 11.0.8, openjsse 1.1.5 ... FAIL ... as expected
OpenJDK 8u275, npn bootstrap 1.9 ... FAIL ... as expected
OpenJDK 8u232, npn bootstrap 1.9.payara-p1 ... SUCCESS
OpenJDK 8u275 ... SUCCESS
OpenJDK 11.0.8 ... SUCCESS
npn is not released yet
npn is now staged as 2.0.0, which can be used to do the build
The build passed locally with profile -Pstaging now, so after npn will make it to Maven Central it should pass now also on Travis :-)
Fixes #2016 and #2111
This is a aggregated PR of Payara's fork of 2.4.4, I hope I didn't skip anything. Current Payara 5.2020.7-SNAPSHOT with these commits in it's own patch of Grizzly passed following tests:
Merge: