That was my expectation: you don't want an installer, you just want to ship a JRE. That's a very different problem which has some more straightforward solutions.
And in any case, even if you want to use an installer, you'll need to cover the inclusion of a JRE similarly to how you'd cover it in a zip.
We really should start working with the fact that on end users machines there is no java at all.
Embedding a JRE in an RCP application has been available for a long time and isn't really Tycho-specific. The most basic approach is to add a `-vm` in your config.ini with the path to a JRE that'd be in the same zip. p2 has some touchpoints to make this happen as part of a build or installation process easily.
Yeah i know, shipping through our installer our product and also a jre (as a sub dir of our .exe file) is not a problem
That should be easy to do when we generate the right .ini file (and i thought that also the exe file of eclipse would maybe even search for such a sub dir?)
So the problem is more to generate a installer with a jre embedded in it..
So a self extracting zip that then runs also directly a command on that dir. I had hoped that oomph did that already..