On Thu, Sep 3, 2009 at 9:11 AM, Felix Meschberger<[email protected]> wrote: > Jukka Zitting once brought up the idea to split the Sling JIRA project > up into multiple projects. > [...] > On the other hand I think bloating the Sling project with a component for > each maven module does > not make any sense either.
Why not? > 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 ? My gut feeling tells me this looks impractical, and I'm not sure if it solves the problem > In some case this is kind of confusing; for example: which component is > taking care of the launchpad/base module ? Isn't this just moving the question to "which project is taking care of the launchpad/base module"? OK, when the projects are named in a sensible way, it's easy to see, but couldn't we just apply a good naming scheme to the JIRA components? > 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. So why don't we create a JIRA component for each maven module? -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 21 531941, ext 2070
