There's no intent that this change affects the wire protocols or
message formats. If you experience issues, please raise a bug report.
On 5/12/15 7:33 AM, Max Rydahl Andersen wrote:
> On 12 May 2015, at 11:26, Tomaž Cerar wrote:
>> for now controller-client jar compatibility is still set to 1.6 but
>> would be wise to move that to 1.7 if you guys are fine with that.
>> javac supports setting target as current - 2, so we are now on
>> might cause us problems in future for JDK9.
>> If you guys are fine with this, can we move controller-client to
> We (JBoss Tools/Developer Studio) currently targets Java 7 as minimal
> thus we specifically fine with that.
> We might even also move to Java 8, but still interested in knowing
> compatibility limits.
>> On Tue, May 12, 2015 at 11:00 AM, Max Rydahl Andersen
>>> On 6 May 2015, at 1:45, James R. Perkins wrote:
>>>> The time has come. Java 8 is now required on WildFly Core master.
>>> Just a question - does this also imply than any client
>>> with it via the management API using the client libraries needs to
>>> Java 8 ?
>>> Just wondering what level of backwards compatibility we are looking
>>> wildfly-dev mailing list
> wildfly-dev mailing list
Senior Principal Software Engineer
JBoss by Red Hat
wildfly-dev mailing list