yes, sorry, my bad for not having provided the right context. in such context oak-commons would contain plain utility class which are not oak specific (no dependency on org.apache.jackrabbit.oak..) while oak-base would contain utility classes that relate to oak specific stuff.
Regards, Tommaso Il giorno gio 6 apr 2017 alle ore 15:16 Angela Schreiber <anch...@adobe.com> ha scritto: > hi davide > > actually we don't have oak-base :-) > the mail might be a bit out of context... we only have it in a poc. > > you may want to take a look at that initial draft > https://github.com/mreutegg/jackrabbit-oak/tree/m12n > but please note that it is still heavily under construction... basically > we just want to see how far we get with some limited effort. > > angela > > > > > On 06/04/17 15:09, "Davide Giannella" <dav...@apache.org> wrote: > > >On 06/04/2017 11:11, Tommaso Teofili wrote: > >> (and eventually oak-commons / oak-base) > > > >I wasn't aware of oak-base. What about a bundle oak-api which exports > >the APIs on which other bundles should rely on? > > > >D. > > > > > >
