Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] shipping directly a jre with an eclipse product on OSX

Ok, i have this approach working now for me.
Windows and Linux worked quite "out of the box"

But i want to say this on the list (and hopefully also it is then found by google) that for OSX you really need to do one more bit because else that jre will not work.

We did get this exception when use use in our Eclipse product Runtime.exec() or ProcessBuilder.start() error=0, posix_spawn failed
at java.lang.ProcessImpl.forkAndExec(Native Method) ~[?:?]
at java.lang.ProcessImpl.<init>(Unknown Source) ~[?:?]
at java.lang.ProcessImpl.start(Unknown Source) ~[?:?]
at java.lang.ProcessBuilder.start(Unknown Source) ~[?:?]
at java.lang.Runtime.exec(Unknown Source) ~[?:?]
at [j2db_server_2019.6.0.3500_rc.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]
at java.util.concurrent.ThreadPoolExecutor$ Source) [?:?]
at Source) [?:?]

When testing we did see if we just got (the same) tar.gz file from adoptopenjdk and we pointed the vm to that one it did work..
So with quite a search we finally found the difference there is a "jspawnhelper"  binary in the lib folder that needs to have the executable bit set...   

So i added that also the the p2.inf.template:

and made sure that the tar.gz file that we generate as an "installer" of our product also sets the right executable bits on that file.

Why is it if you generate through tycho a tar.gz file that the executable bit is not set on "eclipse" binary?
And would it be possible that what we mention now i the p2.inf, for the java and jspawnhelper binaries, that that is also ending up in the product.tar.gz file? (even if you are on windows building it)

Because currently even if you use tar.gz files as an output format, then extracting that won't start it because of the missing executable flags. 
"java" is for osx or linux not really needed because the vm arg does point to a .dylib or .so but on osx we do need that jspawnhelper to be executable.


On Tue, 30 Apr 2019 at 13:03, Mickael Istria <mistria@xxxxxxxxxx> wrote:

I've made some experiments of a more "p2-native" way to embed a JRE some time ago, hoping it will allow one day to ship a JRE with Eclipse IDE directly (but this is currently stuck for legal reason).
In , you can see in the "runtime" folder some p2 units that include a JRE (OpenJ9+OpenJDK from AdoptOpenJDK in that case), and have touchpoints to set the `-vm` flag for the product when they're installed. With this approach, just including those units in your product make it use the included JRE. A cool thing is that the JRE is then a regular p2 unit, so it can be uninstalled and updated like anything else, without any specific workflow.
It was only tested on Linux and would require update to newer AdoptOpenJDK build to support macOS.
It's a piece of work that's currently stalled on my end because I'm waiting for legal approval before spending more effort on it. If you're going to use it, you can just copy it, it's EPL. And if you do, please consider writing a good blog post about it as I think this approach deserve to be made more popular ;)

tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Johan Compagner

Back to the top