Modern Android supports modern Java language features: http://stackoverflow.com/questions/20480090/does-android-support-jdk-6-or-7
If someone in the community contributes well-scoped patches to allow jclouds 1.8.x to work better on older Android we can merge those but otherwise jclouds 2.0 should remain Java 7-only for its previously-discussed benefits. On Mon, Oct 06, 2014 at 08:57:19AM -0700, Adrian Cole wrote: > 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 -- Andrew Gaul http://gaul.org/
