You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2015/10/23 12:29:27 UTC

[jira] [Commented] (OAK-3544) o.a.j.o.api should not depend on Guava

    [ https://issues.apache.org/jira/browse/OAK-3544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14970782#comment-14970782 ] 

Chetan Mehrotra commented on OAK-3544:
--------------------------------------

IMHO depending on third party classes from API signatures is bad and something to avoid but depending on tested Guava utilities in implementation is fine. Do not see a reason to avoid using them for implementation even in API classes

> o.a.j.o.api should not depend on Guava
> --------------------------------------
>
>                 Key: OAK-3544
>                 URL: https://issues.apache.org/jira/browse/OAK-3544
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>              Labels: technical_debt
>
> The o.a.j.o.api has multiple dependencies on classes exported by the Google Guava bundle. The the o.a.j.o.api package should be made independent from Google Guava.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)