These bindings add to jclouds maintenance and make evolving core APIs harder. Further they really belong outside of the jclouds repository. I would like to remove these in 2.1.0
+1 to remove. It should be easy enough to keep them in a separate repository dependent on jclouds, if desired. Is there something like a code scan for potential usage that we could run?
Regards ap
