Hi all
Jukka Zitting once brought up the idea to split the Sling JIRA project
up into multiple projects. At that time we opted not to do it.
I want to bring back this idea on the table.
In the Sling project we have almost 99 maven projects. Some of which
have a corresponding component in the Sling JIRA project. Most don't.
In some case this is kind of confusing; for example: which component is
taking care of the launchpad/base module ? On the other hand I think
bloating the Sling project with a component for each maven module does
not make any sense either.
So I think we should probably split the Sling JIRA project into several
projects along the general SVN structure lines:
* Sling Launchpad/SLINGLAUNCHPAD (all launchpad modules)
* Sling Core/SLINGCORE (api, engine, ...)
* Sling JCR/SLINGJCR (including jcr install)
* Sling Commons/SLINGCOMMONS
* Sling Scripting/SLINGSCRIPTING
* Sling Servlets/SLINGSERVLETS (might also be merged in Core)
* Sling Extensions/SLINGEXT
all projects would be part of the Sling project category.
WDYT ?
Regards
Felix
