On 6/25/2019 1:44 PM, Scott Palmer wrote:
I just tried this out. One thing that has changed since my last testing was the
“create-installer” vs “--package-type” parameter.
“--package-type all” isn’t allowed. If I want to create .rpm and .deb, or
.exe. and .msi, do I need to run twice now?
Yes - the new model is that only one artifact generated by each
invocation of the jpackage command. To build both artifacts now
requires running the tool twice. This avoids a problem in the previous
implementation when one package type succeeded and another failed.
Maybe this could be a comma separated list or the --package-type parameter
could be specified multiple times?
This also doesn’t address the issue on macOS where the the typical distribution
of a .pkg file is in a .dmg image. On macOS you typically have either an
Application Bundle (the raw macOS app image) in a .dmg, or an installer package
(.pkg) in a .dmg. I’ve never seen a .pkg distributed on it’s own, though I
guess there is no reason it couldn’t be. Unlike the Application Bundle, an
installer package really is a single file.
Yes - we are still discussing what the best collection of package types
is on Macosx, and this should be addressed in a future EA build.
The --help output on macOS ends with the line “Platform dependent options for
creating the application package:” with no options listed after that. Are
there options for setting the background graphic image of the installer package
and different images for each flavour of .dmg? The .dmg with the Application
Bundle should be able to have a different background image than the .dmg with a
.pkg installer. The most common contents of the Application Bundle .dmg are a
alias to the Applications folder and an arrow graphic on the background to
suggest dragging the app bundle to the Applications folder. For a installer
package no such arrow image would be needed, though you may have a graphic with
some instructions, or just branding imagery.
Currently there are no “Platform dependent options for creating the
application package:”, but this seems like a good suggestion to add one.
Would "mac-dmg-image" or "mac-dmg-background" be an appropriate option
name for such an option ?
/Andy
Regards,
Scott
On Jun 24, 2019, at 2:31 PM, Andy Herrick <andy.herr...@oracle.com> wrote:
The next EA build of JPackage is available at https://jdk.java.net/jpackage/
This build ( jdk-14-jpackage+1-8 ) is the first early access release based on
JDK-14
This release contains fixes to the following issues:
JDK-8225428: CLI change to remove "mode", rename to "package", and build only
one target
JDK-8226191: jpackager --license-file option broken on windows for jdk
installers.
JDK-8225569: jpackage app-image layout
JDK-8224132: Investigate feasibility of doing SQE code coverage runs for
jpackage
JDK-8225092: Several jpackage tests failes when run with jcov enabled
JDK-8221333: Replace Inno Setup with custom MSI wrapper for .exe bundler
JDK-8226193: BundleNameTest and BundleIdentifierTest fails if run without
network connection
JDK-8223643: Provide better defined context for custom installer steps on
Windows
JDK-8223402: Create tests for some Mac installer specific options
JDK-8225023: JPackageCreateAppImageBundleNameTest fails
JDK-8223038: JPackage code signing fails on Mac.
JDK-8223318: jpackage --mac-bundle-name option doesn't work
JDK-8223080: Build team code review requests.
JDK-8223212: Code cleanup found during jpackage review
JDK-8223586: remove jpackage dead code and other cleanup
JDK-8223953: Fix CLASSPATH parsing for sub-directorys containing spaces
JDK-8224748: --add-launcher option --add-modules
JDK-8222901: different behavior when --name option not used
JDK-8223241: jpackage cleanup from code review
JDK-8223333: Use try-with-resources where feasible
JDK-8224130: create additional automated tests for create-app-image
JDK-8223334: Additional cleanup in jpackage tool
JDK-8224116: populate jpackage manual tests for Linux
JDK-8223700: Create markdown file for jpackage man pages
JDK-8223189: Fix trailing whitespace and whitespace only file modification.
JDK-8223321: jpackage ToolProvider is not thread-safe
JDK-8226532: cleanup is not called when jpackage command fails.
JDK-8224597: create automated tests for platform create-app-image options
please send feedback to core-libs-dev@openjdk.java.net
/Andy Herrick
