|Re: [cbi-dev] MacOS notarization|
After reviewing the the file https://git.eclipse.org/c/nattable/org.eclipse.nebula.widgets.nattable.git/tree/org.eclipse.nebula.widgets.nattable.examples.e4.product/pom.xml I can say you are missing signerUrl parameter to your eclipse-macsigner-plugin. See https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.tychoeclipsebuilder/sdk/pom.xml#n122 on how we did it in platform
There are multiple stages in the notarization process
From the message I suspect you may be missing step 3. In step 3 we specify explicit signer url. Please use that other wise you will not have secure timestamp ot hardened runtime enabled
Hope this helps
thanks for the hint. It seems that really the issue was that I tried to trigger to notarization from the download area. Moving it to the Jenkins area works. But now I get errors from the notarization service.
The signature does not include a secure timestamp.
The executable does not have the hardened runtime enabled.
The binary is not signed.
I have added the following to the pom.xml of the product project.
The cbi-version is 1.1.8-SNAPSHOT. Any idea why the created dmg file seems to be incorrect?
On Wed, May 20, 2020 at 3:03 PM Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Back to the top