Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8259742 | 17 | Jonathan Gibbons | P2 | Resolved | Fixed | b06 |
JDK-8260130 | 16.0.1 | Jonathan Gibbons | P2 | Resolved | Fixed | b03 |
The fix for JDK-8245956 has exposed an underlying bug JDK-8258246.
It is too late and risky to fix the underlying bug for 16, so we should backout the change forJDK-8245956 until JDK-8258246 has been fixed.
It is too late and risky to fix the underlying bug for 16, so we should backout the change for
- backported by
-
JDK-8259742 Revert JDK-8245956 JavaCompiler still uses File API instead of Path API in a specific case
- Resolved
-
JDK-8260130 Revert JDK-8245956 JavaCompiler still uses File API instead of Path API in a specific case
- Resolved
- relates to
-
JDK-8258246 sun.net.www.ParseUtil.decode throws java.lang.IllegalArgumentException: Error decoding percent encoded characters
- Open
-
JDK-8245956 JavaCompiler still uses File API instead of Path API in a specific case
- Closed
-
JDK-8259646 JavaCompiler still uses File API instead of Path API in a specific case (Round 2)
- Open
(2 links to)