I took some inspiration from Apache Aries for this hierarchical maven structure. It has very fine granular OSGi modules (not that we have to do that too) and still keeps everything in one hierarchical Maven project.
With a hierarchical maven project structure you can build/ test/ install either all of the projects in one go or just one of them. I don’t think that it makes sense to have multiple separated maven projects for OAK. There will always be dependencies on each other and with a hierarchical structure these are kept in one place. And you need some kind of “root” bundle that loads all dependencies within an OSGi container. In the OAK case most likely oak-jcr or oak-core. On 07/08/15 11:31, "Thomas Mueller" <[email protected]> wrote: >Hi, > >I have nothing against modularization, I'm just against "modularization = >create many many Maven projects". I prefer modularization *within* one >project. Why can't we do that instead? > >>Ideally you have a ³root² project, e.g. >> >>/oak >> /security >> /api >> /implementationA >> /implementationB >> /core >> /persistence >> /.. > >That looks like a Java *package* structure to me. The Wikipedia article >you mentioned is not about Maven projects, but about modularity in general. > >Regards, >Thomas >
