jclouds has stalled on upgrading our Guava dependency[1] due to our Karaf dependency. Our team lacks the background and volunteers lack the time to resolve this despite over a year of discussion. I propose removing jclouds-karaf and jclouds-cli from the build and posting notices in the README and user mailing lists. When a volunteer can resolve this we can reintegrate this support.
Some background on why this is important: our Guava dependency has repeated annoyed users it used to have an aggressive deprecation policy and jclouds depended on @Beta APIs. Newer versions of Guava depend on Java 8 but our Karaf version seems to have an incompatibility. Attempts to upgrade it have failed. As a matter of strategy, I think jclouds should narrow its focus since many of the more active developers, including me, now split our time with other projects. We should consider removing some of the labs providers and other incomplete efforts to reduce the maintenance burden. As a concrete suggestion, I would like to remove the jdbc labs provider. [1] https://issues.apache.org/jira/projects/JCLOUDS/issues/JCLOUDS-1333 -- Andrew Gaul http://gaul.org/
