Yes then it the eclipse executable (in jre/Contents/MacOS) has the X flag set
And also "java" in jre/Contents/Home/bin/
But the weird part is the jspawnhelper in jre/Contents/Home/lib hasn't...
So now i am wondering why there is a difference between java and jspawnhelper
because it has to he the touchpoint/chmod call that does it
(because all executable bits coming from the original download of adoptopenjdk is already lost when creating the feature.zip file)
So why wouldn't my second line in the p2.inf work...:
org.eclipse.equinox.p2.touchpoint.natives.chmod(targetDir:${installFolder}/features/com.servoy.jre.macosx.x86_64.feature_12.0.0/jre/Contents/Home/bin/,targetFile:java,permissions:755);
org.eclipse.equinox.p2.touchpoint.natives.chmod(targetDir:${installFolder}/features/com.servoy.jre.macosx.x86_64.feature_12.0.0/jre/Contents/Home/lib/,targetFile:jspawnhelper,permissions:755);
But anyway i can't rely on this because our product is also build on window machines and the output should always be exactly equal
So i keep my current ant script:
<tar destfile="${project.build.directory}/servoy_osx.tar.gz" compression="gzip" longfile="gnu">
<tarfileset dir="${project.build.directory}/osx_installer/" filemode="755" >
<include name="Eclipse.app/Contents/MacOS/servoy"/>
<include name="**/jre/Contents/Home/lib/jspawnhelper"/>
<include name="**/jre/Contents/Home/bin/*"/>
<include name="firstuse.command"/>
<include name="**/*.sh"/>
</tarfileset>
<tarfileset dir="${project.build.directory}/osx_installer/">
<exclude name="**/jre/Contents/Home/lib/jspawnhelper"/>
<exclude name="**/jre/Contents/Home/bin/*"/>
<exclude name="Eclipse.app/Contents/MacOS/servoy"/>
<exclude name="firstuse.command"/>
<exclude name="**/*.sh"/>
</tarfileset>
......
</tar>
to fix all the executable bits for our installer.
But i wonder if i now do an upgrade, so that install will do an P2 update to a next version and we ship a new jre, will it then set the executable bit on the new jspawnhelper....
Will have to test this somehow
johan
