Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Building on JDK 11 fails with "No password supplied for PKCS#12" #5808
I believe this has happened before and was solved, but I can't find an actual solution. As far as I know I have a default JDK 11 install on my Ubuntu 18.04.3 and am bootstrapping the clone of this repo.
jruby 184.108.40.206-SNAPSHOT (2.5.3) 2019-08-01 5627c8f OpenJDK 64-Bit Server VM 11.0.4+11-post-Ubuntu-1ubuntu218.04.3 on 11.0.4+11-post-Ubuntu-1ubuntu218.04.3 +jit [linux-x86_64]
Edit: observed same behavior on 19.04
After a successful
I believe this is related: https://bugs.openjdk.java.net/browse/JDK-8194702
This appears to have a fix in Java 14, but I thought I saw this starting to get backported to earlier versions: https://bugs.openjdk.java.net/browse/JDK-8162628
And there's a workaround here you might try: robolectric/robolectric#5115 (comment)
To set that property at a JRuby command line use something like this:
Or put the
Sorry to see you've run into this but it seems like a JDK issue and we've never found a clean workaround we can do on the JRuby side.
That workaround doesn't seem to work for me, with either Java 11 or Java 13:
still fails in the same way.
Another workaround, from one of the issues you linked, which is to use
also doesn't work. I've also tried exporting the JAVA_OPTS so different JVM invocations would all pick them up.
A workaround that does work is to simply switch to Java 8, run
My current versions:
You know it occurs to me that this is happening during gem installs during our build, which is done using an earlier JRuby version. I think we have worked around this issue in recent JRuby releases, since I can't reproduce by installing gems at a command line.
I will confer with @mkristian on that angle and see if we can do another upgrade of the "mavengem" plugin and other build-time uses of JRuby.