Hi, Am Dienstag, den 13.05.2008, 08:30 +0200 schrieb Carsten Ziegeler: > Hi, > > it seems that we are nearly through - so this could be the last part of > the series for now :)
Great !! > I think the remaining part is the "sling" directory. I'm not sure if > this contains some extensions we could move to the extensions dir? Wasn't that part of an earlier "Cleaning up our modules" approach ? > And I think we should find a better name than "sling" for this directory > as everything is Sling :) (it made sense when we distinguished between > micro sling and sling). So any good idea? Sorry, no. Except perhaps "Catapult" ;-) > 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. We should take care to not add more - e.g. like I did adding the sling/core dependency, which was really a bad idea. Regards Felix
