<div dir="ltr"><div><div><div><div>Max,<br><br></div>for now controller-client jar compatibility is still set to 1.6 but it would be wise to move that to 1.7 if you guys are fine with that.<br>see: <a href="https://github.com/wildfly/wildfly-core/blob/master/controller-client/pom.xml#L44">https://github.com/wildfly/wildfly-core/blob/master/controller-client/pom.xml#L44</a><br><br></div>javac supports setting target as current - 2, so we are now on border and might cause us problems in future for JDK9.<br><br></div>If you guys are fine with this, can we move controller-client to 1.7?<br><br><br><br>--<br></div>tomaz<br><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 12, 2015 at 11:00 AM, Max Rydahl Andersen <span dir="ltr"><<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 6 May 2015, at 1:45, James R. Perkins wrote:<br>
<br>
> The time has come. Java 8 is now required on WildFly Core master.<br>
<br>
</span>Just a question - does this also imply than any client communicating<br>
with it via the management API using the client libraries needs to run<br>
Java 8 ?<br>
<br>
Just wondering what level of backwards compatibility we are looking at.<br>
<span class="HOEnZb"><font color="#888888"><br>
/max<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>
</div></div></blockquote></div><br></div>