Hi I have the impression, that this imght solve your short-term issue but in the long term you actually dilute modularity in that you integrte a single, special MK implementation into Oak Core.
I may be way off the current implementation, but from a modularization POV this sounds perfectly wrong. Regards Felix Am 18.06.2013 um 07:31 schrieb Chetan Mehrotra: > I wanted to make use of the new Whiteboard support [1] for publishing > Cache related MBeans and for Scheduler Service. I see two options > > 1. Move the Whiteboard support to oak Commons > 2. Move MongoMk to Oak Core > > Similar requirement was felt for use of StringCache in MongoMK [2]. > There also it was suggested to move Mongo MK to Oak Core. So should we > move the codebase to Oak Core and change the package from > o.a.j.mongomk to o.a.j.oak.plugins.mongomk > > Chetan Mehrotra > > [1] https://issues.apache.org/jira/browse/OAK-867 > [2] https://issues.apache.org/jira/browse/OAK-861
