thanks - i would also prefer to stick with a single POM (that's why I started this thread).
however, keep in mind that for sling models we also would like to use bnd and the bnd plugins for the models metadata, I assume that's not possible with tinybundles. i will play with it a bit more and experiment with it. keeping a single POM would really be a great benefit, even if we probably have to sacrifice a bit of comfort to create/register new test sling models e.g. by registering them manually. after all, the main goal in the current stage of stability of those modules, is to keep the integration tests alive and running, and not necessarily to make it as easy as possible to add tons of new integration tests and test models - as long as it's documented how to do it instead for the ITs. stefan > -----Original Message----- > From: Robert Munteanu <[email protected]> > Sent: Thursday, January 15, 2026 2:51 PM > To: [email protected] > Subject: Re: Move integration tests to impl project - sling models impl > > 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
