[
https://issues.apache.org/jira/browse/OAK-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved OAK-6125.
-------------------------
Resolution: Later
> Consider hierarchical module structure
> --------------------------------------
>
> Key: OAK-6125
> URL: https://issues.apache.org/jira/browse/OAK-6125
> Project: Jackrabbit Oak
> Issue Type: Task
> Reporter: angela
>
> Quote from [~mduerig] on the original m12n thread on oak-dev:
> {quote}
> Looking at the list of modules, its size and the names, did you consider
> switching to a hierarchical module structure? Or could this make sense
> later on? Otherwise can we come up with a naming scheme that implies
> grouping (e.g. node store implementations, blob store implementations,
> etc.)
> {quote}
> Possible candidates as Michael already mentioned:
> - "getting-started": {{oak-examples}} and {{oak-exercise}}
> - "blob": {{oak-blob}}, {{oak-blob-plugins}}, {{oak-blob-cloud}} and
> {{oak-blob-clould-azure}}
> - "node store": {{oak-store-spi}}, {{oak-segment-tar}} and later on also
> document store implementations
> Additionally I think of the following:
> - "query": {{oak-lucene}}, {{oak-solr-core}}, {{oak-solr-osgi}} and possibly
> the query and index code from {{oak-core}} if we would manage to isolate that
> - "security": {{oak-auth-external}}, {{oak-auth-ldap}},
> {{oak-authorization-cug}} and possibly the security-spi and default impl if
> we would manage to isolate that from oak-core.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
