Mabe this could help…
javac -source 1.7 -target 1.7 -bootclasspath /usr/lib/jvm/java-7-oracle/jre/lib/rt.jar
Am 11.02.2015 um 23:23 schrieb Scott Marlow <smarlow(a)redhat.com>:
On 02/10/2015 05:03 PM, Tomaž Cerar wrote:
>
> On Tue, Feb 10, 2015 at 10:52 PM, Scott Marlow <smarlow(a)redhat.com
> <mailto:smarlow@redhat.com>> wrote:
>
>
> The Java 8 TCK update is for EE 6, not EE 7. The EE 7 TCK might
> also pass with Java 8 (we should try that independent of which Java
> version we require).
>
> Aha, this is what i was interested in.
> Any chance you can try with JDK8 against current master?
Doing this now.
>
>
> Scott, can you confirm this?
>
>
>> From the EE 7 platform specification:
>
> "
> EE.9.5
>
> Requirements for All Java EE Profiles
>
> The Java Platform, Standard Edition 7 is the required foundation for
> any Java EE 7 profile.
>
> Yes, but that doesn't say that is the only version that is required.
>
> *EE.2.4.1 Container Requirements*
> "This specification requires that containers provide a Java Compatible™
> runtime environment, as defined by the Java Platform, Standard Edition,
> v7 specification (Java SE)."
>
> Which means any Java runtime that is compatible with v7 is fine, and as
> far as we know 8 is backward compatible, as it provides all v7 does and
> more.
Being able to run with Java 7 is what I get out of either the profile or
the container requirements, both seem to state the requirement for V7.
This sounds like a question for the EE 7 expert group (perhaps they
didn't really mean that Java 7 could be used to run an EE 7 implementation).
>
>
>
>
> _______________________________________________
> 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