[ 
https://issues.apache.org/jira/browse/SLING-12131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784163#comment-17784163
 ] 

Rob McDougall commented on SLING-12131:
---------------------------------------

{quote}A quick google turned up that the OpenRewrite projct
{quote}
I've used this before and it works well, but I haven't used it for custom 
@Rules (which I would imagine don't migrate well).
{quote}There are custom @Rule implementations that are non-trivial to migrate. 
There are runners, that may not be trivial to migrate, either. The difference 
between assertions and some ootb \{{@Rule}}s can likely be covered with 
automation.
 
{quote}
Well, complete conversion to JUnit5 Jupiter should not be required before the 
JUnit4 can be removed. Conversion to JUnit5 Vintage Engine should handle custom 
@Rules and whatever other JUnit4 constructs are being used. That's all I am 
talking about. Once that is done, the dependency on the unmaintained JUnit4 is 
removed. Conversion from Vintage to Jupiter can take as long as it takes.

> Update sling-parent pom.xml to include JUnit5 dependencies
> ----------------------------------------------------------
>
>                 Key: SLING-12131
>                 URL: https://issues.apache.org/jira/browse/SLING-12131
>             Project: Sling
>          Issue Type: Task
>            Reporter: Rob McDougall
>            Priority: Major
>
> JUnit4 is in maintenance mode (no updates in the last 2 years and then only 
> security fixes).  I think updating projects to JUnit5 should be encouraged.
> I am thinking this should be a relatively easy change of adding the 
> junit-jupiter and junit-vintage-engine into the Dependency Management section 
> of the sling-parent.
> Once this is done, individual projects could switch to the vintage-engine (at 
> the very least) or move to jupiter by switching the dependency in their 
> project pom.
> Some day down the road, the JUnit 4 dependencies could be removed.  Projects 
> that have not updated to JUnit5 (vintage or jupiter) by that time are likely 
> no longer maintained.



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

Reply via email to