[wildfly-dev] wildfly 8 client library now requires Java 7 ?

[Kabir Khan]

WildFly 8 targets JEE7, which must be runnable on JDK 7 (we build WF with JDK7).
EAP 6.2 targets JEE6, which must be runnable on JDK 6.
On 13 Sep 2013, at 12:04, Ståle W. Pedersen wrote:

> sorry for sidetracking this, but can someone explain to me why we still 
> are using java6? - epecially for wildfly8...!
> 
> if the reason is because the largest userbase still use java6 then i beg 
> to question if noone are "forcing" them to upgrade they wont. its human 
> nature. if we as a "cutting edge" company cant force customers to use a 
> product that was first released in july 2011 then im curious who will...
> 
> sorry for the rant, probably caused by me playing with jdk8 and would 
> really like to start using it before 2015....
> 
> ståle
> 
> On 13.09.13 12:07, Max Rydahl Andersen wrote:
>> I bumped into this error while trying out wildfly 8.
>> 
>> An internal error occurred during: "Starting wildfly-8.0.0.Alpha4".
>> org/jboss/as/controller/client/helpers/standalone/DeploymentPlanBuilder : Unsupported major.minor version 51.0
>> 
>> Seems like the client library we use to control present and past servers now require Java 7.
>> 
>> Is this expected ?
>> 
>> We can go back using older libraries for JBoss AS 7/EAP 6 and would have to mark that you can't actually talk with
>> Wildfly 8 libraries without Java 7 - but before doing that I wanted to check if this is expected or not?
>> 
>> Thanks,
>> /max
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev