Open davidcockbill opened 1 month ago
We've never signed anything on our side, maybe the Scala guys did sign JLine on their side somehow ?
Hi gnodet,
Thanks for your reply. You are probably correct about Scala signing JLine. For now I have a workaround; but I guess the intent of the original bug still stands. If this artefact is to be built into a Mac application it should really be signed.
Thanks, Dave.
You are probably correct about Scala signing JLine
I don't think so, we don't do anything special with JLine, it's just an ordinary dependency. (I am the Scala 2 release manager.)
Seth, thanks for your valued knowledge!
I am trying to notarize a dmg and it is failing due to libjlinenative.jnilib not being signed.
For my application, jline is brought in as a transitive dependency by scala-compiler
Running
mvn org.apache.maven.plugins:maven-dependency-plugin:3.4.0:tree
:Notarize works:
Notarize broken:
The error in questions is as follows (sensitive details changed to protect the guilty):
Essential libjlinenative.jnilib is not signed. This occurs both on Intel and Arm.
If I override the transitive
jline
version to pull in the latest version (3.26.2) it still fails. If I pull in the latestscala-compiler
and overridejline
with version 3.24.1 the notarize is a success.