<p dir="ltr">I ran into issues with using Java 8 to run my build but targeting Java 7 for most artifacts. I would highly suggest applying a solution based on AnimalSniffer or supplying the Java 6/7 tools.jar for bootclasspath to javac. Helps catch these types of issues</p>
<div class="gmail_quote">On Apr 17, 2015 8:04 AM, "Darran Lofthouse" <<a href="mailto:darran.lofthouse@jboss.com">darran.lofthouse@jboss.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Quick warning for anyone developing using Java 8 but on projects still<br>
dependent on Java 7.<br>
<br>
Normally this is fine, as an engineer you make sure you don't use any<br>
new language features or call new APIs and generally it all works.<br>
<br>
With Java 8 there is one addition gotcha, Java 8 adds support for<br>
default method implementations on interfaces, to add to this some<br>
pre-existing methods have now been replaced with default<br>
implementations. The side effect being it is easy to miss that you have<br>
a method missing from a class and it will not be picked up till it is<br>
compiled on Java 7.<br>
<br>
e.g. On java.util.Iterator the remove method is now default so classes<br>
that implement this interface no longer need to implement that method<br>
unless they really are providing an implementation of that method.<br>
<br>
Regards,<br>
Darran Lofthouse.<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div>