Re: [epp-dev] unable to provide M5 build - config.a.jre.javase

[Mickael Istria <mistria@xxxxxxxxxx>]

On Fri, Feb 2, 2018 at 10:14 AM, Markus Knauer <mknauer@xxxxxxxxxxxxxxxxx> wrote:

- Instead of using only the staging Photon p2 repository (which includes the missing IUs), I added for testing purposes the Platform M5 repo as an additional repository. Not that I expected a difference, but I wanted to have this tested, too.

I tried the exact same thing a few minutes ago :)

- As another test I added a hard dependency from the product IU epp.package.cpp (i.e. the CPP packages) to the exact version of config.a.jre.javase, but that didn't help either. I reverted that change after the test.

Ok.

So first thing I noticed is that the build fails quite late. So the (config.)a.jre.javase 9.0.0 is resolved when doing target-platform resolution. So it's available in the general context of the build and we can focus inverstiagation on the materialize-product step.

Then I noticed that /home/mistria/git/org.eclipse.epp.packages/packages/org.eclipse.epp.package.cpp.product/target/targetPlatformRepository/ which is used as an input for the director/materialize-product step contains the (config.)a.jre.javase 1.7.0 . So the error given by p2 about missing a.jre.javase 9.0.0 is correct, there isn't such installable unit. So we can lower the rank of p2 on the list of potential culprits.

Now, why would thise /home/mistria/git/org.eclipse.epp.packages/packages/org.eclipse.epp.package.cpp.product/target/targetPlatformRepository/ contains a.jre.javase? I'm investigating what can make Tycho generate specifically this version for the director instead of the 9.0.0 one which is used in target-platform resolution.
At this point, it can either be a bug in Tycho materialize-products mojo, or some configuration to tweak in EPP. I keep investigating.