[bisq-network/bisq] Upgrade JavaFX to v15 (#4242)

Christoph Atteneder notifications at github.com
Tue Oct 6 08:02:08 UTC 2020


> @ripcurlx No experience with that yet, but it seems like `jpackage` could handle that as well (via `--mac-sign` / `--mac-signing-keychain` / `--mac-signing-key-user-name`, see [documentation](https://docs.oracle.com/en/java/javase/14/docs/specs/man/jpackage.html)).
> 
> Should I extend the script to ask for user input for these options and then pass them along to `jpackage`? (I assume the main thing is a path to the signing key, then maybe a signing username or identifier) Or do you have separate tools with which you want to do the signing, so we should not modify the packaging script for that purpose?

Wasn't able to do this yesterday. I'll try to add it manually first to see if it works.
I would not ask it as an option in the final implementation, but rather check if an environment variable is set, so the release process needs as little user input as possible.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/4242#issuecomment-704101810
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20201006/c561d13f/attachment.html>


More information about the bisq-github mailing list