[
https://issues.apache.org/jira/browse/SLING-9930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239292#comment-17239292
]
Oliver Lietz commented on SLING-9930:
-------------------------------------
Yes, I'm trying to understand why the ITs are not part of the main project
(pom) and why you use the {{maven-invoker-plugin}}. Looks like a lot of
boilerplate to me.
The changes I had to do in the IT repo were minimal and you could also stick to
Testing PaxExam 3.1.0 by removing the bundle (option) from base configuration.
> Move sling-servlets-annotations-it tests to sling-servlets-annotations module
> -----------------------------------------------------------------------------
>
> Key: SLING-9930
> URL: https://issues.apache.org/jira/browse/SLING-9930
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Affects Versions: Sling Servlet Annotations 1.2.4
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: Sling Servlet Annotations 1.2.6
>
>
> Having the ITs in a different Git repository creates a slower feedback loop
> and makes the tests less visible.
> As recently done for
> [https://github.com/apache/sling-org-apache-sling-adapter-annotations], I'll
> move the integration tests to the sling-servlets-annotations module using
> maven-invoker-plugin.
> I'll use the [{{PaxExamServer}}-based
> tests|https://github.com/apache/sling-org-apache-sling-servlets-annotations-it/tree/SLING-9929]
> for that as they are stabler than the ones from the current {{master}}
> branch (where the Sling startup sometimes fail in testing).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
