[
https://issues.apache.org/jira/browse/SLING-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289466#comment-16289466
]
Oliver Lietz commented on SLING-7298:
-------------------------------------
bq. That is all I care about right now in the context of the validation IT.
That's a pity. Sling Launchpad hides a lot of issues in Sling and Oak related
to dynamism and concurrency due to the use of start levels and a slow booting
process.
bq. ...and I am done.
You're obviously not. You have to implement features which are already
available in OPS4J Pax Exam (the de facto standard for OSGi testing) and
Sling's Testing PaxExam module. Also with new Tinybundles 3 removing
{{org.apache.sling.validation.test-services}} would have been quite easy
(moving it into {{org.apache.sling.validation.core}}).
> 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.4
>
>
> Due to issues with pax-exam with the newest Oak 1.6.0 (described in
> https://www.mail-archive.com/[email protected]/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)
