-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b157
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8175669 | 10 | Robert Field | P2 | Resolved | Fixed | b02 |
The most important one is the ability to supply a fileManager. While
JShell uses runtime platform supplied Filemanager, the user code may
target a different JDK (patch release, for example); I need the ability
to analyse and compile against the exact runtime used afterwards to run
the code.
Similar to that is a change in JdiInitiator; again, the calling IDE
needs to specify "home" property in order to invoke VM from the correct
JDK installation. Running / testing user applications on specific patch
releases may be very important.
JShell uses runtime platform supplied Filemanager, the user code may
target a different JDK (patch release, for example); I need the ability
to analyse and compile against the exact runtime used afterwards to run
the code.
Similar to that is a change in JdiInitiator; again, the calling IDE
needs to specify "home" property in order to invoke VM from the correct
JDK installation. Running / testing user applications on specific patch
releases may be very important.
- backported by
-
JDK-8175669 JShell API: not patch compatible
-
- Resolved
-