For sure many thanks. Getting stable builds and keeping them there is key. And supporting the newer JVMs in a timely manner is as well.
Thanks! On Wed, Mar 23, 2022 at 8:51 AM Kevin Doran <[email protected]> wrote: > Thanks for your contributions David, Mike, and Paul! These are all great > updates. > > On Mar 17, 2022 at 15:04:32, David Handermann <[email protected] > > > wrote: > > > Development Team, > > > > Thanks to reviews from Mike Thomsen and Paul Grey, support for building > the > > NiFi project on Java 17 is now in the main branch. > > > > The GitHub continuous integration workflow now includes a fourth > > environment: > > > > Ubuntu Zulu JDK 17 EN > > > > Although some dependencies may cause runtime issues with Java 17, this > new > > build target will help highlight and correct particular issues. For the > > purpose of compatibility, restricted reflective access is one of the most > > important differences in Java 17. Java 11 flags these issues as illegal > > reflective access warnings, but Java 17 prevents these operations. > > > > New issues with particular components should be flagged and addressed > using > > the standard Jira tracking process. > > > > This is also a good time to mention ongoing work related to JUnit 5. Big > > thanks to Mike Thomsen for working through numerous modules and multiple > > rounds of feedback to update a majority of components to JUnit 5! All new > > test code should use JUnit 5 org.junit.jupiter components. Some work > still > > remains to convert various modules, which can be tracked through > sub-tasks > > under the following Jira issue: > > > > https://issues.apache.org/jira/browse/NIFI-9084 > > > > Finally, shout out to Paul Grey for his efforts to improve the > reliability > > of the NiFi system tests on GitHub. The resource-constrained GitHub > > runners can expose test stability problems that are difficult to track > > down, but thanks to Paul's work, the stability of the system tests on > > GitHub has improved. > > > > Regards, > > David Handermann > > >
