Hi, Bertrand Delacretaz schrieb: >> ...Maybe we would have to start and stop Sling differently. Eg. by >> launching a separate process with Sling standalone and shutdown that >> instance after the tests. Such setup could be hooked into the >> pre-integration-test and post-integration-test phases.... > > Can't we just use a specific system property to set the sling.home > value for integration tests? > > We could use "sling.integration.testing.home" for example, to make it > clear what that is, and this property would override any other > setting, logging a warning when that happens. > > Seems reasonably foolproof and simple to implement, or am I missing something? > > Redoing our testing infrastructure just for this reason feels a bit > like overkill to me.
This sounds like so, yes. But having a special system property coded into Sling just for the sake of keeping the current integration tests just does not sound right either. In fact, I truly dislike special casing, of which such a property would be an instance ;-) Another workaround, we could try would be to replace the original web.xml file of the Sling web app with a specially crafted one. But, this is kind of fragile, too. Regards Felix
