Details
-
Type:
Umbrella
-
Status: Open
-
Priority:
Trivial
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
Description
Musings (as subtasks) on experimental ideas for when JRE8 is a viable runtime.
| 1. | [JDK8] Unit tests pass |  |
Open | Unassigned | |
| 2. | [JDK8] Refactoring for lambda | |
Open | Unassigned | |
| 3. | [JDK8] Nashorn scripting environment for server side Javascript | |
Open | Unassigned | |
| 4. | [JDK8] GPU redirection | |
Open | Unassigned | |
| 5. | [JDK8] Replace use of high-scale-lib counters with intrinsic facilities | |
Open | Unassigned |
Activity
Yep, just some thoughts on what might be possible, transcribed to JIRA for posterity (if it comes around).
Show
Andrew Purtell
added a comment - Yep, just some thoughts on what might be possible, transcribed to JIRA for posterity (if it comes around).
What's an actual feasible timeline for anyone running JDK8?
I would guess three years. HBase (as a project in some form) has been around since 2007 so could conceivably be still going then.
Probably it will also be possible to run on the bleeding edge in 2.
Show
Andrew Purtell
added a comment - - edited What's an actual feasible timeline for anyone running JDK8?
I would guess three years. HBase (as a project in some form) has been around since 2007 so could conceivably be still going then.
Probably it will also be possible to run on the bleeding edge in 2.
What's an actual feasible timeline for anyone running JDK8? Most of the above improvements seem like they would only be supported on JDK8 and no earlier versions... seems to me that we wouldn't be able to drop Java6 and Java7 support for at least 3-4 more years at the earliest.