[
https://issues.apache.org/jira/browse/NIFI-8427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Thomsen resolved NIFI-8427.
--------------------------------
Resolution: Not A Problem
nifi-mock was refactored to use JUnit 5 ~ 1.15.3. JUnit 4 will stay on the
classpath until the entire code base has been refactored to not use it, but it
shouldn't be an issue for third parties developing custom components who don't
want to use JUnit 4.
> Remove JUnit dependency from nifi-mock
> --------------------------------------
>
> Key: NIFI-8427
> URL: https://issues.apache.org/jira/browse/NIFI-8427
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: John Mark
> Priority: Major
>
> nifi-mock currently has a dependency on JUnit 4. This forces users to include
> JUnit 4 in their build. This is not desirable for those who are not already
> using JUnit 4. For example, JUnit 5 has been out for a long time now, and
> those who use JUnit 5 don't want to have JUnit 4 on the test classpath. It
> pollutes the classpath and causes confusion. Those who use other test
> frameworks may also not want to be forced to include JUnit 4.
> nifi-mock should not be dependent on any third party libraries or frameworks
> like this. Errors can be reported using custom Exceptions or Errors instead.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
