Bug 1193553
Summary: | Web container isn't able to compile JSPs containing JDK 8 specific code (lambda expressions) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Radim Hatlapatka <rhatlapa> | ||||||
Component: | Web | Assignee: | Rémy Maucherat <rmaucher> | ||||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Michael Cada <mcada> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 6.4.0 | CC: | cdewolf, dandread, jawilson, jdoyle, jmartisk, jurikolo | ||||||
Target Milestone: | ER3 | ||||||||
Target Release: | EAP 6.4.0 | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 1194436 (view as bug list) | Environment: | |||||||
Last Closed: | 2019-08-19 12:41:03 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | 1194560, 1194562 | ||||||||
Bug Blocks: | 1194436 | ||||||||
Attachments: |
|
Description
Radim Hatlapatka
2015-02-17 15:25:19 UTC
It would also need JDT 4.4. I see no actual user benefit, so dev- for 6.4.0. @Remy, how can we NAK something like this while saying we support Java 8? This is not about running on Java 8, it is about putting some Java 8 code in webapps sources. But anyway, if it is a blocker, someone needs to set the blocker flag. Tomaz Cerar <tomaz.cerar> updated the status of jira WFLY-4362 to Coding In Progress The primary reason our customers will want to move to Java 8 is because Oracle Java 7 goes EOL in April 2015, not because they re-wrote their applications to use lambda expressions. So IMO this can be release noted and solved in a CP. For upstream fix is two part. 1) fix the jastow (jasper fork for undertow) to allow source & target to be 1.8 PR for that: https://github.com/undertow-io/jastow/pull/15 2) update ecj to 4.4.1 in wildfly PR for wildfly is pending jastow release. Very well then, changing the dev flag. Created attachment 993682 [details]
new reproducer web app
In the previous example war there wasn't caught IOException causing that it would fail even after JDK 1.8 compilation fix. Updating the example with correct web app.
I removed the blocker flag. If we can get this into ER3 then let's do that. If we cannot get it in that build, and need another build, then it can go there. If ER3 is the GA, then let's target it for a CP. The update to ECJ 4.4 is not risky at all, it is a compiler with very high use, and is already integrated in Tomcat. Verified with EAP 6.4.0.ER3 |