RFR: JDK-8212780: JEP 343: Packaging Tool Implementation (original) (raw)
Andy Herrick andy.herrick at oracle.com
Tue Nov 13 14:56:43 UTC 2018
- Previous message: RFR: JDK-8212780: JEP 343: Packaging Tool Implementation
- Next message: JDK 12 RFR of JDK-6304578: (reflect) toGenericString fails to print bounds of type variables on generic methods
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 11/12/2018 6:36 PM, Alan Snyder wrote:
Can someone say whether the two-step package creation feature is implemented and explain how to use it?
Yes -
1.) "jpackager create-image -o output -n app-name ..."
2.) "jpackager create-installer -o installer-output -n installer-name --app-image 'output\app-name' ..." (windows)
"jpackager create-installer -o installer-output -n installer-name --app-image 'output/app-name.app' ..." (for mac)
"jpackager create-installer -o installer-output -n installer-name --app-image 'output\app' ..." (for linux)
What is the plan for documentation? The command line help is inadequate.
Yes - there will be further documentation, it's content and form are still under discussion.
/Andy
On Oct 26, 2018, at 1:09 PM, Alan Snyder wrote:
I noticed the following statement in the JEP: In this latter case, the tool can either create a native package from a previously created application image, or it can create a native package directly. I cannot tell from the command summary whether this option has been implemented or not. Without this feature, the ability to create a signed DMG is not very useful, except in the case where the tool creates exactly the right application image. Alan
- Previous message: RFR: JDK-8212780: JEP 343: Packaging Tool Implementation
- Next message: JDK 12 RFR of JDK-6304578: (reflect) toGenericString fails to print bounds of type variables on generic methods
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]