java.lang.NullPointerException: Cannot invoke "java.io.PrintStream.println(String)" because "this.out" is null

[Dustinhoefer]

Hey :)

I am trying to package my updater with jpackage. Unfortunately, only the packaging part works well, starting the application afterwards leads to the above mentioned error message. Here is the Stacktrace:

at org.update4j.service.DefaultUpdateHandler.clearln(DefaultUpdateHandler.java:153)
at org.update4j.service.DefaultUpdateHandler.failed(DefaultUpdateHandler.java:74)
at org.update4j.ConfigImpl.doUpdate(ConfigImpl.java:396)
at org.update4j.Configuration.update(Configuration.java:915)

Caused by calling: config.update(UpdateOptions.archive(path));

Path path = Paths.get("C:/Program/update.zip");

The provided path does exist. I think this might be a problem with the packaged jar inside an .exe file.
The update.zip file is saved next to the jar first, before moving it to the provided path. Is this correct?
Is there a workaround for the file to immediately be created at the path location?

EDIT:

After some looking around I also found that there is a possible NPE (which I am actually running into right now).
ConfigImpl line 396 "handler.failed(t)" internally calls the DefaultUpdateHandler.clearln. This printStream has not yet been initialized, if in the ConfigImpl some error occurs before line handler.startDownloads(); (which initializes this printStream).

Until this is fixed, I can only wonder what the real problem of my code is. I created a ticket.

Kind regards
Dustin

[mordechaim]

You may pass a path that doesn't exist to config.update(), it will create the file. I'm not sure what causes it, as, as you correctly found, there's an exception in the exception reporting itself, thus masking the real cause.

Thanks for the issue you opened. I'll look into it when I have a chance. Meanwhile, you might try to create your own UpdateHandler to capture the exception yourself.

[Dustinhoefer]

I will create a PR soon. Fixed it in my fork.

This is the exception I am getting (which I know how to fix :) )

Accessing the archive depends on the jdk.zipfs module which is missing from the JRE image.