[
https://issues.jboss.org/browse/JBIDE-20010?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-20010:
-------------------------------------
Most, if not all these examples target EAP 6, which implements the Java EE 6 spec. And
[according to that
spec|https://jcp.org/en/jsr/detail?id=316] :
{quote}Java EE 6 is the Enterprise Edition of version 6 of the Java platform, and thus
will be built on Java SE 6.{quote}
JBT/JBDS requires Java 8 to run, but is still capable of launching runtimes with various
versions of Java, so no, the examples should not be changed. However, I suggest [~sgilda]
to document the quickstarts about that warning. More precisely the examples compile with a
target version of 1.6, but a higher version of Java is used to compile. The problem here
is you might be able to use API from JDK 8 that would break at runtime when running with
Java 6. eg. System.lineSeparator() would be available during compilation but isn't
available on in Java 6. So users either need to change the minimum Java requirement in
their pom.xml or make sure Java 6 is an available Java Runtime in the Eclipse
preferences.
JBT 4.3.0.beta1/JBDS 9.0.beta1 require Java8 - but examples once
installed raise warnings as Java6 is not found
---------------------------------------------------------------------------------------------------------------
Key: JBIDE-20010
URL:
https://issues.jboss.org/browse/JBIDE-20010
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.3.0.Beta1
Reporter: Len DiMaggio
Assignee: Fred Bricon
Attachments: Screenshot-6.png
See the attached screenshot - this is not a new issue, but seeing as how we now require
Java 8 (
http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Beta1.html...)
- the examples should no longer reference Java6.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)