You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2021/01/11 09:26:00 UTC
[jira] [Resolved] (SLING-10028) Do no longer manage version of
JMock nor any other mocking framework
[ https://issues.apache.org/jira/browse/SLING-10028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved SLING-10028.
-------------------------------------
Resolution: Fixed
Fixed in https://github.com/apache/sling-parent/commit/f9dc40c7e40a5f38e5bb360efe7afa16b5e06673.
> Do no longer manage version of JMock nor any other mocking framework
> --------------------------------------------------------------------
>
> Key: SLING-10028
> URL: https://issues.apache.org/jira/browse/SLING-10028
> Project: Sling
> Issue Type: Improvement
> Components: General
> Affects Versions: Parent 40
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Parent 41
>
>
> Currently a pretty outdated version of JMock is managed in the parent pom.xml ([https://github.com/apache/sling-parent/blob/96e3aa372ae124d0ab982d9c3fe560766f2d5ede/sling-parent/pom.xml#L1024).|https://github.com/apache/sling-parent/blob/96e3aa372ae124d0ab982d9c3fe560766f2d5ede/sling-parent/pom.xml#L1024)/]
> In different Sling modules different mocking libraries are used but IMHO Mockito has probably the most usages. As the mocking frameworks are not used consistently I would suggest to no longer manage any versions of mocking frameworks in parent.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)