Felix Meschberger wrote:
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 ?
No, we only moved eventing and scheduling to extensions but didn't
discuss the other things.
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" ;-)
Hehe, +1 :) Ok, seriously, looking at the contents we have there core,
i18n, httpauth, bundleresource, servlet-resolver,servlets-get,
servlets-post.
Most of them are central and it wouldn't make much sense to start Sling
without them (except of course you provide an alternative
implementation). I consider all of them except i18n and httpauth to be
central. So I suggest we move i18n and httpauth to extensions (please
note that this change does not come with any other requirements like
changing artifacts or packaging, so it's just a simple move)
Bertrand suggested to name all of this "core-components" which I think
is a much better name than "sling". This dir would then contain the core
itself and the most important bundles (except the jcr and scripting stuff).
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?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
