RFR: JDK-8212780: JEP 343: Packaging Tool Implementation
kevin.rushforth at oracle.com
Wed May 1 23:17:22 UTC 2019
I got most of the way through the platform-independent Java code today.
Here is my feedback so far.
NOTE: I don't think any of these need to be addressed prior to
integration, so you can either fix them in a follow-on webrev or file a
bug for fixing after integration.
* Several files (e.g., Arguments.java) have unused imports that can be
removed. Maybe this can be done along with expanding wild-card imports.
* I see that jdk.jpackage requires java.desktop. It looks like this is
only needed by the Linux installers to get the size of application
icons. If so, then perhaps this dependency could be moved to
* Should JPackageToolProvider::run log the exception it catches?
Although normal error handling shouldn't throw exceptions, it might be
* The following will prefix the version message with "jpackage version "
private static final String version = bundle.getString("MSG_Version")
+ " " + System.getProperty("java.version");
Similar tools such as jlink and jmod don't prefix their output, but
instead simply print the value of the "java.version" property.
* It would be helpful to add a comment to highlight its usage. Also, for
classes such as this where it is not expected that anyone should create
an instance, a private constructor might be useful?
* The following two constants can be (default) package-scope, since it
isn't used outside the package (and if it were, the BundlerParamInfo
class would need to be public in order for it to be useful) :
public static final BundlerParamInfo<Boolean> CREATE_APP_IMAGE =
public static final BundlerParamInfo<Boolean> CREATE_INSTALLER =
* The "hasAppImage" field is set but not used (which might be OK, unless
you meant to use it for argument validation)
* This file could use a class comment
* What is the purpose of the following?
If it really is needed, a comment would be helpful.
* The following on line 195 could use try-with-resources:
PrintStream out = new PrintStream(cfgFileName);
* IMAGES_ROOT can be package-scope
* Spelling error on line 36
> or as an intermeadiate step in "create-installer" mode.
should be "intermediate"
* In extractFlagsFromVersion, other than throwing an exception, is there
a need to pattern match older JDK versions? The minimum that jpackage
needs to support is JDK 11, so we should be able to assume JEP 322
compliant version numbers. Might this allow for a simplification?
* I think the following comment is obsolete, since the support for the
"JavaFX-Application-Class" jar manifest entry is no longer in jpackage:
// Note we look for both JavaFX executable jars and regular
// As long as main "application" entry point is the same it is main
// (i.e. for FX jar we will use JavaFX manifest entry ...)
More information about the core-libs-dev