Actually, it seems the 2.0 branch has started to use java 7 constructs
internally, which will make jclouds definitely incompatible with android.

For example, it is ok for code to expose alternate paths that use java 7 or
even 8 (ex how okio still works is that these methods are not called in
android and therefore ignored).  However, core shared code can't and still
remain android compatible.

Copying in developer list just so folks know the impact of using trt with
resources :) If we switch to a manner in which java 7 or 8 is optional (no
pun intended), android still has a chance.

-A

Reply via email to