Hi, Am Dienstag, den 13.05.2008, 13:04 +0200 schrieb Carsten Ziegeler: > Felix Meschberger wrote: > >> And the last thing I noticed is that commons testing now contains > >> references to other sling modules which is a little bit against the idea > >> of commons being independent from Sling. As the testing stuff is about > >> jcr testing, we could move it to the jcr modules? > >> (This one is not that important though) > > > > There are two, actually: Sling API and Sling JCR API. Both are API-only > > bundles and both are present because the commons/testing bundle > > implements Mock classes for the respective APIs. I am fine with these > > dependencies. > Yes, they're fine and make sense of course. Would you mind if we move > the testing stuff from commons to jcr?
Yes, because providing a JCR repository instance is just part of the module. It also contains mocks for OSGi and Sling API interfaces, both of which have nothing to do with JCR. We could of course split into three: OSGi mocks, Sling API mocks and the JCR stuff and distribute accordingly. But I am not sure, whether this is really worth the effort. Regards Felix
