[m12n] remove oak-core dep in oak-blob-*

[Tommaso Teofili <to...@gmail.com>]

Hi all,

as part of refactoring and making more appropriate interdependencies I
think it'd be good if we could have that oak-blob-* modules depend on just
oak-blob (and eventually oak-commons / oak-base) and cut their dependency
to oak-core so that they would only rely on the purposely exposed
blob/datastore specific APIs.

WDYT?

Regards,
Tommaso

Re: [m12n] remove oak-core dep in oak-blob-*

[Robert Munteanu <ro...@apache.org>]

On Thu, 2017-04-06 at 10:11 +0000, Tommaso Teofili wrote:
> Hi all,
> 
> as part of refactoring and making more appropriate interdependencies
> I
> think it'd be good if we could have that oak-blob-* modules depend on
> just
> oak-blob (and eventually oak-commons / oak-base) and cut their
> dependency
> to oak-core so that they would only rely on the purposely exposed
> blob/datastore specific APIs.
> 
> WDYT?

+1

I think we should depend as little as possible on oak-core, as a
general rule.

Ideally this would in the end would become a 'leaf' bundle, with no
exported API.

Robert

Re: [m12n] remove oak-core dep in oak-blob-*

[Tommaso Teofili <to...@gmail.com>]

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 <an...@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" <da...@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.
> >
> >
>
>

Re: [m12n] remove oak-core dep in oak-blob-*

[Angela Schreiber <an...@adobe.com>]

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" <da...@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.
>
>

Re: [m12n] remove oak-core dep in oak-blob-*

[Davide Giannella <da...@apache.org>]

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.