neilcsmith-net commented on issue #6052:
URL: https://github.com/apache/netbeans/issues/6052#issuecomment-1604299339

   Thanks @uurazzle - that's good to know.  I also downloaded Apparency and 
verified the two on my M1 test machine.
   
   The NBPackage app bundle task and the scripts in the main repository have a 
different approach to finding libraries (inc. those bundled in JARs) to sign.  
NBPackage also uses the hardened runtime.
   
   
https://github.com/apache/netbeans-nbpackage/blob/master/src/main/java/org/apache/netbeans/nbpackage/macos/MacOS.java
   
https://github.com/apache/netbeans-nbpackage/blob/master/src/main/java/org/apache/netbeans/nbpackage/macos/AppBundleTask.java
   
   vs
   
   
https://github.com/apache/netbeans/blob/master/nbbuild/installer/mac/newbuild/commonfiles/signNativeBinaries.sh
   
   I wondered if something had changed in the list of files, particularly if 
something just on x86_64, but that doesn't seem to be the case as far as I can 
tell.  Anyway, Apache NetBeans 17 also reports the same issue after 
installation.
   
   It's curious that everything is passing notarization anyway.  Another 
potential issue in the ASF installer is the `populate_caches` script -
   
   
https://github.com/apache/netbeans/blob/master/nbbuild/installer/mac/newbuild/commonfiles/postinstall/populate_caches.sh
   
   This seems to be trying to launch from the wrong location, and then writing 
to a file called `exiting` in the root of the app.  That might be breaking the 
signature?
   
   > If the application bundle remained constant you can create your own 
package installer and it simply updates the previous version since the 
name/path is the same vs having to add additional scripting/workflow to remove 
the previous version name.
   
   Yes, all the Codelerity installers are set to do in-place upgrades.  It 
seems the more sensible option now we're releasing every 3 months.
   
   > Let me know if you need me to test anything else.
   
   Thanks!  I'm going to check about using NBPackage to build a macOS bundle 
without JDK, and some testing of that would be useful.  If that works, this is 
another reason to consider using that for NetBeans 19.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Reply via email to