The more stuff we can get running on JDK 1.6, the better. However, there is no
reason to ride roughshod over functionality we *need* available only in JDK7
but such cases must be known, documented and should not be cluttering usage
experience.
If that helps, I can create AEROGEAR jira to add animal-sniffer-plugin [1] to
aerogear-parent to ensure projects are using API JDK of a specific version
(configurable per project) and send PR.
Karel
[1]
http://mojo.codehaus.org/animal-sniffer-maven-plugin/usage.html
On Tue, 07 Jan 2014 09:17:48 -0500
Summers Pittman <supittma(a)redhat.com> wrote:
Karel brought up the fact that the Android project relies on classes
from Java 7. I would like for the Android project to compile using JDK
6, but I was wondering what the rest of the project thought.
For a little back story, until recently the dexer (Android Java byte
code to Dex byte code compiler) could only consume Java 6 byte code.
That was very recently fixed and almost all Java 7 features are
supported on Android version greater than Gingerbread. The exception is
try with resources which is only supported on KitKat.
I havn't looked at the project yet to even get an idea for how much work
it would be, but I suspect it will be rather minimal.
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev