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

--
- DML

_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev