@demobox TL;DR; it would only hurt us to not move to animal sniffer to enforce Java language level 6. The project already has too many ways to break, or slow us down, without adding any value.
Square and google open source projects use animal sniffer to watch out for api level concerns for libraries they want to work on JRE 6 or android. https://github.com/google/guice/blob/master/pom.xml#L269 https://github.com/square/okhttp/blob/master/pom.xml#L206 I don't think requiring the project to be built with JDK 6 is a long-term win. We already hacking to allow filesystem to conditionally compile. Moreover, we've already documented this approach https://issues.apache.org/jira/browse/JCLOUDS-747 Also we've noted that checking signatures is something we haven't yet done, but should. http://wiki.apache.org/jclouds/Coding%20Standards "Note that jclouds Maven configuration prevents incorrect use of newer language features but not newer APIs (yet). " --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/617#issuecomment-64810125
