If a deployment is compiled with Java 8 and uses classes that use Java 8 features, it will log a warning, but may work depending on whether or not that classes functionality depends on annotations.
If a deployment is compiled with Java 8 and uses Java 8 features in the same class as one with EE annotations, the deployment will not be recognized and will fail to deploy.
With this change, Java 8 syntax and annotations in same class will not cause deployment warnings or problems.
Created attachment 992247[details]
jdk8-with-failure.tar.gz
If a deployment is compiled with Java 8 and uses classes that use Lambda's (a Java 8 feature), it will log a warning, but still work.
If a deployment is compiled with Java 8 and uses Lambda's in the same class as one with EE annotations, the deployment will not be recognized. See attached jdk8-with-failure.zip.
This happens regardless of ZIP or RPM install because scanning is done on deployment.
Attaching jdk8-with-warning.tar.gz that demonstrates the warning attached as warning.txt for the cases where EE annotated classes use other classes that use Java 8 syntax.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-0673.html
Created attachment 992247 [details] jdk8-with-failure.tar.gz If a deployment is compiled with Java 8 and uses classes that use Lambda's (a Java 8 feature), it will log a warning, but still work. If a deployment is compiled with Java 8 and uses Lambda's in the same class as one with EE annotations, the deployment will not be recognized. See attached jdk8-with-failure.zip. This happens regardless of ZIP or RPM install because scanning is done on deployment.