[
https://issues.apache.org/jira/browse/SLING-12131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784113#comment-17784113
]
Rob McDougall commented on SLING-12131:
---------------------------------------
> Testing dependencies are never transitive and therefore should not affect
> simple consumers of any Sling bundles!
My point is not really related to testing dependencies. My point is that
unmaintained projects will have outdated dependencies that cause work for
developers. A reliable indicator that a project is unmaintained is that it
does not move to JUnit5. This means that removal of Junit4 after some finite
period causing breakage is an indicator that the project is unmaintained. Do
we want to keep an obsolete dependency in the parent pom for the sole purpose
of allowing unmaintained projects to compile?
If the answer to that question is "yes", then my question would be for how
long? If the answer to that is "forever", then that says that you don't intend
to ever prune unmaintained projects. That doesn't sound like a reasonable
stance to me,
If the answer is for some finite period, then that would mean that it would be
safe to remove an obsolete dependency (in this case JUnit 4) after that finite
period (whatever it is).
> 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)
