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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

In the WildFly codebase it is only the protocol and controller-client modules needed for this, these are intentionally quite minimal so I personally don't see a problem with having them target 1.6. The other dependencies are mostly David's so I'll let him comment on if they are usable in JDK 6 :-) [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ wildfly-controller-client --- [INFO] org.wildfly:wildfly-controller-client:jar:8.0.0.Beta1-SNAPSHOT [INFO] +- org.wildfly:wildfly-protocol:jar:8.0.0.Beta1-SNAPSHOT:compile [INFO] | +- org.jboss.marshalling:jboss-marshalling:jar:1.4.0.Final:compile [INFO] | +- org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta1:compile [INFO] | +- org.jboss.sasl:jboss-sasl:jar:1.0.3.Final:compile [INFO] | +- org.jboss.xnio:xnio-api:jar:3.1.0.CR7:compile [INFO] | \- org.jboss.xnio:xnio-nio:jar:3.1.0.CR7:compile [INFO] +- org.jboss:jboss-dmr:jar:1.2.0.Final:compile [INFO] +- org.jboss.logging:jboss-logging:jar:3.1.3.GA:compile [INFO] +- org.jboss.logging:jboss-logging-annotations:jar:1.2.0.Beta1:provided [INFO] +- org.jboss.logging:jboss-logging-processor:jar:1.2.0.Beta1:provided [INFO] | \- org.jboss.jdeparser:jdeparser:jar:1.0.0.Final:provided [INFO] +- org.jboss.threads:jboss-threads:jar:2.1.1.Final:compile [INFO] +- junit:junit:jar:4.11:test [INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test [INFO] \- org.wildfly:wildfly-build-config:jar:8.0.0.Beta1-SNAPSHOT:compile On 13 Sep 2013, at 11: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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

What about NIO2 stuff that xnio uses? On Fri, Sep 13, 2013 at 5:48 PM, David M. Lloyd <david.lloyd(a)redhat.com <mailto:david.lloyd@redhat.com>> wrote: I've been building things with 1.7 and targeting them to 1.6 via seven2six. So the following should all be 1.6 compatible (if they aren't then please let me know because it's a bug): * org.jboss.marshalling:jboss-marshalling:jar:1.4.0.Final * org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta1 * org.jboss.sasl:jboss-sasl:jar:1.0.3.Final * org.jboss.xnio:xnio-api:jar:3.1.0.CR7 * org.jboss.xnio:xnio-nio:jar:3.1.0.CR7 * org.jboss:jboss-dmr:jar:1.2.0.Final * org.jboss.logging:jboss-logging:jar:3.1.3.GA <http://3.1.3.GA> * org.jboss.logging:jboss-logging-annotations:jar:1.2.0.Beta1 * org.jboss.logging:jboss-logging-processor:jar:1.2.0.Beta1 * org.jboss.jdeparser:jdeparser:jar:1.0.0.Final * org.jboss.threads:jboss-threads:jar:2.1.1.Final In reality there is no actual benefit to the Java 7 class file format (other than simply preventing execution on 6 that is) so whenever possible I just transform my stuff to 1.6 (it's all otherwise compatible). On 09/13/2013 05:46 AM, Kabir Khan wrote: > In the WildFly codebase it is only the protocol and controller-client modules needed for this, these are intentionally quite minimal so I personally don't see a problem with having them target 1.6. > The other dependencies are mostly David's so I'll let him comment on if they are usable in JDK 6 :-) > > [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ wildfly-controller-client --- > [INFO] org.wildfly:wildfly-controller-client:jar:8.0.0.Beta1-SNAPSHOT > [INFO] +- org.wildfly:wildfly-protocol:jar:8.0.0.Beta1-SNAPSHOT:compile > [INFO] | +- org.jboss.marshalling:jboss-marshalling:jar:1.4.0.Final:compile > [INFO] | +- org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta1:compile > [INFO] | +- org.jboss.sasl:jboss-sasl:jar:1.0.3.Final:compile > [INFO] | +- org.jboss.xnio:xnio-api:jar:3.1.0.CR7:compile > [INFO] | \- org.jboss.xnio:xnio-nio:jar:3.1.0.CR7:compile > [INFO] +- org.jboss:jboss-dmr:jar:1.2.0.Final:compile > [INFO] +- org.jboss.logging:jboss-logging:jar:3.1.3.GA:compile > [INFO] +- org.jboss.logging:jboss-logging-annotations:jar:1.2.0.Beta1:provided > [INFO] +- org.jboss.logging:jboss-logging-processor:jar:1.2.0.Beta1:provided > [INFO] | \- org.jboss.jdeparser:jdeparser:jar:1.0.0.Final:provided > [INFO] +- org.jboss.threads:jboss-threads:jar:2.1.1.Final:compile > [INFO] +- junit:junit:jar:4.11:test > [INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test > [INFO] \- org.wildfly:wildfly-build-config:jar:8.0.0.Beta1-SNAPSHOT:compile > > > On 13 Sep 2013, at 11: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(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev > > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- - DML _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/wildfly-dev

Thanks, David. Max, JIRA for getting rid of the JDK 6 requirement in the relevant modules built in WF itself is https://issues.jboss.org/browse/WFLY-2072. On 9/13/13 11:28 AM, David M. Lloyd wrote: > There are one or two API features that will give you an unsupported > error on JDK 6; everything else is emulated (though XNIO does not use > much NIO.2 stuff because mostly it's junk anyway). > > In particular I removed the 1.6 NIO UDP multicast emulation in 3.1 > because nobody was using it anyway. Now it only works in 1.7+. > > Everything used by WildFly should work in 1.6. > > On 09/13/2013 10:55 AM, Tomaž Cerar wrote: >> What about NIO2 stuff that xnio uses? >> >> >> On Fri, Sep 13, 2013 at 5:48 PM, David M. Lloyd <david.lloyd(a)redhat.com >> <mailto:david.lloyd@redhat.com>> wrote: >> >> I've been building things with 1.7 and targeting them to 1.6 via >> seven2six. So the following should all be 1.6 compatible (if they >> aren't then please let me know because it's a bug): >> >> * org.jboss.marshalling:jboss-marshalling:jar:1.4.0.Final >> * org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta1 >> * org.jboss.sasl:jboss-sasl:jar:1.0.3.Final >> * org.jboss.xnio:xnio-api:jar:3.1.0.CR7 >> * org.jboss.xnio:xnio-nio:jar:3.1.0.CR7 >> * org.jboss:jboss-dmr:jar:1.2.0.Final >> * org.jboss.logging:jboss-logging:jar:3.1.3.GA <http://3.1.3.GA> >> * org.jboss.logging:jboss-logging-annotations:jar:1.2.0.Beta1 >> * org.jboss.logging:jboss-logging-processor:jar:1.2.0.Beta1 >> * org.jboss.jdeparser:jdeparser:jar:1.0.0.Final >> * org.jboss.threads:jboss-threads:jar:2.1.1.Final >> >> In reality there is no actual benefit to the Java 7 class file format >> (other than simply preventing execution on 6 that is) so whenever >> possible I just transform my stuff to 1.6 (it's all otherwise >> compatible). >> >> On 09/13/2013 05:46 AM, Kabir Khan wrote: >> > In the WildFly codebase it is only the protocol and >> controller-client modules needed for this, these are intentionally >> quite minimal so I personally don't see a problem with having them >> target 1.6. >> > The other dependencies are mostly David's so I'll let him comment >> on if they are usable in JDK 6 :-) >> > >> > [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ >> wildfly-controller-client --- >> > [INFO] org.wildfly:wildfly-controller-client:jar:8.0.0.Beta1-SNAPSHOT >> > [INFO] +- >> org.wildfly:wildfly-protocol:jar:8.0.0.Beta1-SNAPSHOT:compile >> > [INFO] | +- >> org.jboss.marshalling:jboss-marshalling:jar:1.4.0.Final:compile >> > [INFO] | +- >> org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta1:compile >> > [INFO] | +- org.jboss.sasl:jboss-sasl:jar:1.0.3.Final:compile >> > [INFO] | +- org.jboss.xnio:xnio-api:jar:3.1.0.CR7:compile >> > [INFO] | \- org.jboss.xnio:xnio-nio:jar:3.1.0.CR7:compile >> > [INFO] +- org.jboss:jboss-dmr:jar:1.2.0.Final:compile >> > [INFO] +- org.jboss.logging:jboss-logging:jar:3.1.3.GA:compile >> > [INFO] +- >> org.jboss.logging:jboss-logging-annotations:jar:1.2.0.Beta1:provided >> > [INFO] +- >> org.jboss.logging:jboss-logging-processor:jar:1.2.0.Beta1:provided >> > [INFO] | \- org.jboss.jdeparser:jdeparser:jar:1.0.0.Final:provided >> > [INFO] +- org.jboss.threads:jboss-threads:jar:2.1.1.Final:compile >> > [INFO] +- junit:junit:jar:4.11:test >> > [INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test >> > [INFO] \- >> org.wildfly:wildfly-build-config:jar:8.0.0.Beta1-SNAPSHOT:compile >> > >> > >> > On 13 Sep 2013, at 11: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(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> >> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev >> > >> > >> > _______________________________________________ >> > wildfly-dev mailing list >> > wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> >> > https://lists.jboss.org/mailman/listinfo/wildfly-dev >> > >> >> >> -- >> - DML >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org <mailto:wildfly-dev@lists.jboss.org> >> https://lists.jboss.org/mailman/listinfo/wildfly-dev >> >> > > -- Brian Stansberry Principal Software Engineer JBoss by Red Hat _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

I've been building things with 1.7 and targeting them to 1.6 via seven2six. So the following should all be 1.6 compatible (if they aren't then please let me know because it's a bug): * org.jboss.marshalling:jboss-marshalling:jar:1.4.0.Final * org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta1 * org.jboss.sasl:jboss-sasl:jar:1.0.3.Final * org.jboss.xnio:xnio-api:jar:3.1.0.CR7 * org.jboss.xnio:xnio-nio:jar:3.1.0.CR7

On 10/9/13 12:25 PM, Rob Stryker wrote: > On 09/13/2013 11:48 PM, David M. Lloyd wrote: >> I've been building things with 1.7 and targeting them to 1.6 via >> seven2six. So the following should all be 1.6 compatible (if they >> aren't then please let me know because it's a bug): >> >> * org.jboss.marshalling:jboss-marshalling:jar:1.4.0.Final >> * org.jboss.remoting:jboss-remoting:jar:4.0.0.Beta1 >> * org.jboss.sasl:jboss-sasl:jar:1.0.3.Final >> * org.jboss.xnio:xnio-api:jar:3.1.0.CR7 >> * org.jboss.xnio:xnio-nio:jar:3.1.0.CR7 >> > > I'm noticing an issue currently. It seems something in xnio requires a > class only available in java7. I'll be re-opening the wfly bug for you > to investigate. > I opened https://issues.jboss.org/browse/XNIO-207 to track that. > java.lang.NoClassDefFoundError: java/lang/ReflectiveOperationException > at org.xnio.ssl.JsseXnioSsl.<init>(JsseXnioSsl.java:81) > at org.xnio.Xnio.getSslProvider(Xnio.java:221) > at > org.jboss.remoting3.remote.RemoteConnectionProvider.connect(RemoteConnectionProvider.java:188) > at > org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:296) > at > org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251) > > > Usecase is running eclipse with java6, then launching wildfly with > java7, but using the features in jbosstools to communicate with the > running server over management API. The jars we're using are: > > <jbossdmr.version>1.2.0.Beta2</jbossdmr.version> > <jboss.logging.version>3.1.3.GA</jboss.logging.version> > <jboss.marshalling.version>1.4.1.Final</jboss.marshalling.version> > <jboss.marshalling.river.version>1.4.1.Final</jboss.marshalling.river.version> > <jboss.remoting.version>4.0.0.Beta1</jboss.remoting.version> > <jboss.sasl.version>1.0.3.Final</jboss.sasl.version> > <jboss.threads.version>2.1.1.Final</jboss.threads.version> > <wildfly.controller.version>8.0.0.Beta1</wildfly.controller.version> > <wildfly.protocol.version>8.0.0.Beta1</wildfly.protocol.version> > <xnio.api.version>3.1.0.CR7</xnio.api.version> > <xnio.nio.version>3.1.0.CR7</xnio.nio.version> > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev > -- Brian Stansberry Principal Software Engineer JBoss by Red Hat _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

i know. i guess i would like a harder cutoff to jdk7. for tooling, why not require jdk7 when its trying to work with wildfly8?

On 13.09.13 13:13, Kabir Khan wrote: >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 &gt;&gt;&gt;wildfly-dev(a)lists.jboss.org >>>https://lists.jboss.org/mailman/listinfo/wildfly-dev >>_______________________________________________ >>wildfly-dev mailing list &gt;&gt;wildfly-dev(a)lists.jboss.org >>https://lists.jboss.org/mailman/listinfo/wildfly-dev >

On Fri, Sep 13, 2013 at 2:13 PM, Kabir Khan <kabir.khan(a)jboss.com&gt; wrote: 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. Not exactly! EE7 requires at least JDK7 not only it has to be runnable on, it is hard requirement! (see EE7 spec chapter 9.5) EAP 6.x targets EE6 which requires at least JDK6 but is also runnable on JDK7.