This PR changes jclouds' OSGi import directive for guava to allow version range [16.x-19.0]. This helps dependent projects mix jclouds with bundles using other guava versions within OSGi environments.
According to https://issues.apache.org/jira/browse/JCLOUDS-622 jclouds was made to use only guava classes that are compatible throughout guava versions, so this should be safe for the time being. What are your thoughs on this? Is there better way to solve this package resolution problem? P.S. The changes are based on the 1.9.x branch, because that's the version we use right now. I can port them to master if needed. You can view, comment on, or merge this pull request online at: https://github.com/jclouds/jclouds/pull/934 -- Commit Summary -- * Improve version range specification for guava -- File Changes -- M project/pom.xml (3) M scriptbuilder/pom.xml (6) -- Patch Links -- https://github.com/jclouds/jclouds/pull/934.patch https://github.com/jclouds/jclouds/pull/934.diff --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/934
