hi 

i looked at the dependencies listed with the oak-core module
and was wondering that it depends on a specific mk implementation,
while i was assuming that oak-core should be independent of the
mk/node store implementation being used.

looking at it in more detail revealed that the dependency is not
needed for the actual implementation but rather for additional
stuff located in the oak-mk module, namely:

- everything in o.a.j.mk.json.*
- everything in o.a.j.mk.blobs.*
- some utilities like Cache, IOUtils and StringUtils

consequently, i would like to propose to reduce the scope of this
dependency to test purpose and refactor the mentioned parts out.

variant a:
move all mentioned packages/classes to dedicated packages in oak-commons.
additional advantages would be that oak-commons would finally get some
justification as currently it just contains 3 utility classes.

variant b:
only move the json and utility related code to oak-commons but create
a new dedicated module for the blob store related code. while this would
look more natural to me, i know that adding new module has been quite
controversial in the past.

i don't have any strong preference for either variant. it tried variant a
as a prove of concept and didn't encounter any obstacles so far.
 
wdyt?

kind regards
angela

 

Reply via email to