Github user rvesse commented on the pull request:
https://github.com/apache/jena/pull/87#issuecomment-123743814
It may be possible to remove the explicit dependency on guava as a stop-gap
If memory serves the reason behind this was that dependency management in
the Jena parents was causing a version conflict. Since guava is no longer a
dependency of other Jena modules (because it is shaded) it may be possible to
simply remove the explicit dependency on Guava
Also completely agree with Andy, even if the tests pass the real test is
that the demo application runs correctly on an actual Hadoop cluster where
various dependencies are provided by the cluster
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
