Thanks – that article on Fetching the Notary Log was exactly what I was looking for. Among other things, the log said: status summary: "Archive contains critical validation errors" status code: 4000 The actual issue seems to be that it has two apparently unsigned JNI libraries packaged in as dependencies: libgluegen-rt and libjnidispatch. I tried re-making the app and dmg from a signed jar (I do my development on Mac but have to sign on Windows) and it gave the same errors. How do I fix this?

Thanks – that article on Fetching the Notary Log was exactly what I was looking for. I tried signing again and looked at the log. The errors seem to boil down to two JNI libraries the app depends on that are apparently unsigned: libgluegen-rt and libjnidispatch. These are not new dependencies, so this must have something to do with the switch to Maven. Is it possible to request signed artifacts from Maven? A quick Google search didn't help.

Thanks – Fetching the Notary Log was exactly what I was looking for. I tried signing again, and it failed again, so I checked the notary log. It seems to be two apparently unsigned JNI libraries that the app depends on: libgluegen-rt and libjnidispatch. These aren’t new dependencies, so it must be related to the switch to Maven. Any idea how to request signed artifacts from Maven? A quick Google search didn’t help.

Thanks. Fetching the Notary Log was exactly what I was looking for. I tried signing again, and it failed again, so I checked the notary log. It seems to be two apparently unsigned JNI libraries that the app depends on: libgluegen-rt and libjnidispatch. These aren’t new dependencies, so it must be related to the switch to Maven. Any idea how to request signed artifacts from Maven? A quick Google search didn’t help.

Thanks – Fetching the Notary Log was exactly what I was looking for. I tried signing again, and it failed again, so I checked the notary log. It seems to be two apparently unsigned JNI libraries that the app depends on: libgluegen-rt and libjnidispatch. These aren’t new dependencies, so it must be related to the switch to Maven. Any idea how to request signed artifacts from Maven? A quick Google search didn’t help.

Thanks! Fetching the Notary Log was exactly what I was looking for. The log told me that two of my Maven dependencies (both JNI) are apparently unsigned. Is there a way to prevent or get around this in future builds?