Hi Stefan, On Mon, 2026-01-12 at 19:11 +0000, Stefan Seifert wrote: > is this the way we want to go? other ideas? personally, i'm fine with > this way - but i would focus on those projects where we can eliminate > separate integration tests projects. i would not start to move the > ITs we currently have as part of our sling starter to all the > individual bundles, then we would have to refactor tons of other > repositories in this way as well.
Thanks for picking this up. I think there is a simpler version of this setup in the OAuth client module [1]. The ITs run against a version of the Sling Starter built with additional local features. There is indeed the problem of managing the additional bundle with the test modules. That could be solved by using an artifact with an additional classifier or by using TinyBundles to package and install the bundle at runtime. That being said, I'm also fine with going the way you have prototyped and we need to be mindful of the additional effort needed to keep using a single module. Thanks, Robert [1]: https://github.com/apache/sling-org-apache-sling-auth-oauth-client
