T ToolboxZX Member Licensed User Longtime User Mar 14, 2023 #1 Just looking for clarification for an old closed thread on this library: https://www.b4x.com/android/forum/threads/sshj-ssh-scp-sftp-for-java.88615/ The original thread talks about the need for setting #MergeLibraries to False due to a signing issue with bouncycastle. However I noticed an edit to the thread at the beginning by Erel: Edit by Erel: You need to add this line for it to work with the built-in packager: #PackagerProperty: VMArgs = --add-opens b4j/org.bouncycastle.jcajce.provider.asymmetric.ec=java.base So on a hunch, I compiled the release with #MergeLibraries: True and built the installer package. Everything seems to work just fine without the need for seperate jars. So I am just attempting to verify if this is the case, that there isn't a signing issue any longer. Thank you.
Just looking for clarification for an old closed thread on this library: https://www.b4x.com/android/forum/threads/sshj-ssh-scp-sftp-for-java.88615/ The original thread talks about the need for setting #MergeLibraries to False due to a signing issue with bouncycastle. However I noticed an edit to the thread at the beginning by Erel: Edit by Erel: You need to add this line for it to work with the built-in packager: #PackagerProperty: VMArgs = --add-opens b4j/org.bouncycastle.jcajce.provider.asymmetric.ec=java.base So on a hunch, I compiled the release with #MergeLibraries: True and built the installer package. Everything seems to work just fine without the need for seperate jars. So I am just attempting to verify if this is the case, that there isn't a signing issue any longer. Thank you.
Erel B4X founder Staff member Licensed User Longtime User Mar 14, 2023 #2 The standalone packager always merges the libraries. I guess that the mentioned requirement is no longer needed. Upvote 0
The standalone packager always merges the libraries. I guess that the mentioned requirement is no longer needed.
