jpackage EA Build 0

[Kevin Rushforth]

 > So I could say drop the jpackage command into my app’s current 
earlier JRE bin directory and it might work?

No. You need to run jpackage from the JDK 12 ea build that you 
downloaded. jpackage isn't something you drop into your application, 
it's a tool you run to package up your application with a Java Runtime. 
By default it uses the Java Runtime from which you run jpackage, but you 
can specify a different Java Runtime to use to bundle with your 
application via:

     jpacakge create-image --runtime-image /somewhere_else/jdk-11 ...

-- Kevin

On 12/14/2018 9:42 AM, Michael Hall wrote:
>> On Dec 14, 2018, at 11:30 AM, Kevin Rushforth <kevin.rushforth at oracle.com> wrote:
>>
>> Correct. jpackage will be delivered as a tool that is part of the JDK. Future EA builds will likely include an EA of JDK 13.
>>
>> -- Kevin
>>
>> On 12/14/2018 9:26 AM, Michael Hall wrote:
>>>> Warning: This build is based on an incomplete version of JDK 12 <https://openjdk.java.net/projects/jdk/12/>.
>>>>
>>> So when I download (OS X) it appears it is included with a entire  jdk 12 build?
> OK thanks, this might take a little figuring out. I haven’t done anything like this for a while.
> If I replace the Plugins/Java.runtime/Contents for my application with the jpackage downloaded idk-12.jdk/Contents directory I get a JRELoadError dialog on launch.
> Are there actual JDK 12 dependencies with the command or is that what it’s being worked on and tested with and there may not actually be 12 dependencies?
> So I could say drop the jpackage command into my app’s current earlier JRE bin directory and it might work?
>