-
Bug
-
Resolution: Fixed
-
P4
-
18
-
b26
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8282489 | 17.0.4-oracle | Sean Coffey | P4 | Resolved | Fixed | b01 |
JDK-8283303 | 17.0.4 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
If e.g. a MultiReleaseException is thrown from VersionHelper.java:60 [1], it will be wrapped in an ExecutionException, and then re-wrapped in an Error in DependencyFinder.java:271 [2].
As a result, the main logic for reporting errors in JdepsTask::run will not recognize the exception and report the error properly [3], resulting in a stack trace with an empty exception message instead (like in the SO question).
Perhaps the cause of the ExecutionException at [2] should be re-thrown instead of wrapping it in an Error.
See https://bugs.openjdk.java.net/browse/JDK-8277165 for a reproducer.
[1] : https://github.com/openjdk/jdk/blob/master/src/jdk.jdeps/share/classes/com/sun/tools/jdeps/VersionHelper.java#L60
[2] : https://github.com/openjdk/jdk/blob/master/src/jdk.jdeps/share/classes/com/sun/tools/jdeps/DependencyFinder.java#L270
[3] : https://github.com/openjdk/jdk/blob/master/src/jdk.jdeps/share/classes/com/sun/tools/jdeps/JdepsTask.java#L549
- backported by
-
JDK-8282489 jdeps does not report some exceptions correctly
- Resolved
-
JDK-8283303 jdeps does not report some exceptions correctly
- Resolved
- relates to
-
JDK-8277165 jdeps --multi-release --print-module-deps fails if module-info.class in different versioned directories
- Resolved
-
JDK-8277564 jdeps --print-module-deps fails with --multi-release
- Closed
- links to
-
Commit openjdk/jdk17u-dev/defd25c9
-
Commit openjdk/jdk/7e54d065
-
Review openjdk/jdk17u-dev/256
-
Review openjdk/jdk17u/314
-
Review openjdk/jdk/6530