[jira] [Updated] (NIFI-11532) Remove JUnit 4 and Groovy Test from Default Dependencies

2023-06-13 Thread David Handermann (Jira)


 [ 
https://issues.apache.org/jira/browse/NIFI-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Handermann updated NIFI-11532:

Fix Version/s: 1.23.0

> Remove JUnit 4 and Groovy Test from Default Dependencies
> 
>
> Key: NIFI-11532
> URL: https://issues.apache.org/jira/browse/NIFI-11532
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0, 1.23.0
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> The root Maven configuration includes JUnit 4 in the list of default project 
> dependencies. With the vast majority of tests migrated to JUnit 5, JUnit 4 
> should be removed from the set of default project dependencies. This includes 
> removing the JUnit Vintage Engine dependency, which provides compatibility 
> for JUnit 4. The few remaining modules with JUnit 4 tests should have 
> declared dependencies on the JUnit Vintage Engine to highlight remaining 
> items for refactoring.
> Following a similar pattern, the Groovy Test dependency should be removed 
> from the list of default project dependencies. the Groovy Test module should 
> be added to the modules with remaining Groovy tests to highlight additional 
> work needed.
> As part of this removal, existing tests that depend on JUnit 4 and Groovy 
> Test libraries should be evaluated for potential removal if the functionality 
> overlaps with other tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (NIFI-11532) Remove JUnit 4 and Groovy Test from Default Dependencies

2023-06-13 Thread Matt Burgess (Jira)


 [ 
https://issues.apache.org/jira/browse/NIFI-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-11532:

Fix Version/s: 2.0.0
   (was: 2.latest)
   Resolution: Fixed
   Status: Resolved  (was: Patch Available)

> Remove JUnit 4 and Groovy Test from Default Dependencies
> 
>
> Key: NIFI-11532
> URL: https://issues.apache.org/jira/browse/NIFI-11532
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> The root Maven configuration includes JUnit 4 in the list of default project 
> dependencies. With the vast majority of tests migrated to JUnit 5, JUnit 4 
> should be removed from the set of default project dependencies. This includes 
> removing the JUnit Vintage Engine dependency, which provides compatibility 
> for JUnit 4. The few remaining modules with JUnit 4 tests should have 
> declared dependencies on the JUnit Vintage Engine to highlight remaining 
> items for refactoring.
> Following a similar pattern, the Groovy Test dependency should be removed 
> from the list of default project dependencies. the Groovy Test module should 
> be added to the modules with remaining Groovy tests to highlight additional 
> work needed.
> As part of this removal, existing tests that depend on JUnit 4 and Groovy 
> Test libraries should be evaluated for potential removal if the functionality 
> overlaps with other tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (NIFI-11532) Remove JUnit 4 and Groovy Test from Default Dependencies

2023-05-09 Thread David Handermann (Jira)


 [ 
https://issues.apache.org/jira/browse/NIFI-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Handermann updated NIFI-11532:

Description: 
The root Maven configuration includes JUnit 4 in the list of default project 
dependencies. With the vast majority of tests migrated to JUnit 5, JUnit 4 
should be removed from the set of default project dependencies. This includes 
removing the JUnit Vintage Engine dependency, which provides compatibility for 
JUnit 4. The few remaining modules with JUnit 4 tests should have declared 
dependencies on the JUnit Vintage Engine to highlight remaining items for 
refactoring.

Following a similar pattern, the Groovy Test dependency should be removed from 
the list of default project dependencies. the Groovy Test module should be 
added to the modules with remaining Groovy tests to highlight additional work 
needed.

As part of this removal, existing tests that depend on JUnit 4 and Groovy Test 
libraries should be evaluated for potential removal if the functionality 
overlaps with other tests.

  was:
The root Maven configuration includes JUnit 4 in the list of default project 
dependencies. With the vast majority of tests migrated to JUnit 5, JUnit 4 
should be removed from the set of default project dependencies. This includes 
removing the JUnit Vintage Engine dependency, which provides compatibility for 
JUnit 4. The few remaining modules with JUnit 4 tests should have declared 
dependencies on the JUnit Vintage Engine to highlight remaining items for 
refactoring.

Following a similar pattern, the Groovy Test dependency should be removed from 
the list of default project dependencies. the Groovy Test module should be 
added to the modules with remaining Groovy tests to highlight additional work 
needed.


> Remove JUnit 4 and Groovy Test from Default Dependencies
> 
>
> Key: NIFI-11532
> URL: https://issues.apache.org/jira/browse/NIFI-11532
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.latest
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The root Maven configuration includes JUnit 4 in the list of default project 
> dependencies. With the vast majority of tests migrated to JUnit 5, JUnit 4 
> should be removed from the set of default project dependencies. This includes 
> removing the JUnit Vintage Engine dependency, which provides compatibility 
> for JUnit 4. The few remaining modules with JUnit 4 tests should have 
> declared dependencies on the JUnit Vintage Engine to highlight remaining 
> items for refactoring.
> Following a similar pattern, the Groovy Test dependency should be removed 
> from the list of default project dependencies. the Groovy Test module should 
> be added to the modules with remaining Groovy tests to highlight additional 
> work needed.
> As part of this removal, existing tests that depend on JUnit 4 and Groovy 
> Test libraries should be evaluated for potential removal if the functionality 
> overlaps with other tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (NIFI-11532) Remove JUnit 4 and Groovy Test from Default Dependencies

2023-05-08 Thread David Handermann (Jira)


 [ 
https://issues.apache.org/jira/browse/NIFI-11532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Handermann updated NIFI-11532:

Status: Patch Available  (was: Open)

> Remove JUnit 4 and Groovy Test from Default Dependencies
> 
>
> Key: NIFI-11532
> URL: https://issues.apache.org/jira/browse/NIFI-11532
> Project: Apache NiFi
>  Issue Type: Sub-task
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.latest
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The root Maven configuration includes JUnit 4 in the list of default project 
> dependencies. With the vast majority of tests migrated to JUnit 5, JUnit 4 
> should be removed from the set of default project dependencies. This includes 
> removing the JUnit Vintage Engine dependency, which provides compatibility 
> for JUnit 4. The few remaining modules with JUnit 4 tests should have 
> declared dependencies on the JUnit Vintage Engine to highlight remaining 
> items for refactoring.
> Following a similar pattern, the Groovy Test dependency should be removed 
> from the list of default project dependencies. the Groovy Test module should 
> be added to the modules with remaining Groovy tests to highlight additional 
> work needed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)