JDK-8140037 : App Bundler: Detect Dependent Module from module path or classpath
- Type: Sub-task
- Component: deploy
- Sub-Component: packager
- Affected Version: 9-repo-jigsaw
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-10-20
- Updated: 2016-06-09
- Resolved: 2016-06-09
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 9 |
|---|
9Fixed  |
Related Reports
|
Relates :
|
Description
Detect the dependent modules from the module path or classpath. In the case of a non-modular or a module both the class path and module path are used to detect all modules required for the jimage. For a non-modular jar jdeps is used. For a module, simply adding it to -addmods of jlink will link all transient dependencies.
Comments
|