[
https://issues.apache.org/jira/browse/SLING-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16285231#comment-16285231
]
Oliver Lietz commented on SLING-7298:
-------------------------------------
[~kwin], the issue is in Oak and not in Pax Exam (Pax Exam has disclosed
several issues in the past) – and the issue has to be fixed in Oak anyway.
Removing the test framework to hide an issue is not very clever. Setting up
Sling Launchpad right for testing seems to be quite tricky, right?
> Validation IT: Use slingstart-maven-plugin in favour of pax-exam
> ----------------------------------------------------------------
>
> Key: SLING-7298
> URL: https://issues.apache.org/jira/browse/SLING-7298
> Project: Sling
> Issue Type: Improvement
> Components: Validation
> Affects Versions: Validation 1.0.0
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Fix For: Validation Core 1.0.2
>
>
> Due to issues with pax-exam with the newest Oak 1.6.0 (described in
> https://www.mail-archive.com/dev@sling.apache.org/msg72805.html) and also
> because leveraging pax-exam with Sling is complex (to get all necessary
> dependencies right) I propose to use the {{slingstart-maven-plugin}} together
> with a custom Sling Launchpad instead. The according model is derived from
> the default Sling 9 launchpad and only two additional bundles are added there.
> In addition the deprecated {{testing.tools}} dependency should be removed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
