[
https://issues.apache.org/jira/browse/OAK-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16840283#comment-16840283
]
Alex Deparvu commented on OAK-7217:
-----------------------------------
Based on the above manual exports I took a look at oak-commons and it seems
there are only 2 classes that have the Guava export problem:
* oak-commons/src/main/java/org/apache/jackrabbit/oak/commons/FileIOUtils.java
*
oak-commons/src/main/java/org/apache/jackrabbit/oak/commons/io/LazyInputStream.java
Continuing this analysis means manually going through all usages and trying to
figure out if they are considered legal or not. Is this useful, or do we need a
more automated approach, something that could eventually be included in a CI
job?
> check public Oak APIs for references to Guava
> ---------------------------------------------
>
> Key: OAK-7217
> URL: https://issues.apache.org/jira/browse/OAK-7217
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Reporter: Julian Reschke
> Priority: Minor
> Attachments: detect-api.diff, extract-guava.sh, guava-global.log,
> guava-public-v2.log, guava-public.log
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
