Github user MartinPayne commented on the issue:
https://github.com/apache/nifi/pull/2780
> The global declaration for JUnit is JUnit 4.12. If someone is using v5,
they'll have to work around that.
Yes, we're using a workaround at the moment. We have to declare JUnit 4 as
a dependency with "test" scope, and configure the Maven Dependency Plugin to
force JUnit 4 as used to prevent it from being reported as a declared and
unused dependency. I would prefer to have the fix upstream so that we can
remove the workaround.
> nifi-mock is designed to support JUnit tests and I'm not aware of any
components that use JUnit 5.
I am using JUnit 5, and I imagine over time many other people will be
migrating to it too. Code wise there is nothing in nifi-mock which means it
shouldn't work with JUnit 5, and I would expect it to work with other test
frameworks too.
I've provided a link to a table of Maven dependency scopes to demonstrate
that this won't result in JUnit ending up in non-test code. Are there any
further concerns about this fix?
---
