Hi, Am Dienstag, den 13.05.2008, 13:04 +0200 schrieb Carsten Ziegeler: > 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)
Agreed. In fact, bundleresource is probably also an extension... We might want to start thinking of required and optional extensions ;-) Because some extensions are required and used by the launchpad and some extensions are just there for demo and other purposes... > > 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). Hmm... I have my reservations with the name "core-components". First it is long - and I don't like long names and second: This would give a groupId of o.a.s.core.components and an bundle symbolic name of org.apache.sling.core.components.core for the (today's) sling/core bundle ... But we could of course rename the sling folder to core and rename the sling/core module to core/engine - because that module essentially contains the main request processing machinery. The question still remains: What is really "core" ? The Sling API in fact would be core, what else ? Maybe we should change completely ? Move sling/core to a top-level engine bundle (besides api the only toplevel bundle. And rename the current sling directory to servlets - because it just contains the servlet resolver as well as the get and post servlets. Regards Felix
