[
https://issues.apache.org/jira/browse/OAK-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435277#comment-16435277
]
Robert Munteanu commented on OAK-7406:
--------------------------------------
[~reschke] - that might be an issue with Maven plug-in inheritance of maybe a
side effect of how the maven-bundle-plugin reads configurations. But I guess
that we don't want automatic inheritance of an export definition - maybe not
all modules use it, but rather a way of saying "when importing
com.google.common.*, use this version range ". Which I don't know can work. IMO
defining the import range centrally and then using the property in specific
modules is OK.
> relax guava version range in Import-Package declarations
> --------------------------------------------------------
>
> Key: OAK-7406
> URL: https://issues.apache.org/jira/browse/OAK-7406
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Reporter: Julian Reschke
> Priority: Major
> Attachments: OAK-7406.diff
>
>
> We should relax the Guava version to the range that we test with, that is
> 15.0 to 21 excl.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
