Impact of a.jre.javase=10.0.0 (was Re: [tycho-dev] Tycho 1.2.0 released)
(too old to reply)
Sievers, Jan
2018-06-06 06:41:16 UTC
a.jre.javase=10.0.0 provides osgi.ee capabilities as well as system packages which may be required by bundles.

p2 products also used to have a perfect version match requirement on this IU but I think that Mickael removed that in the p2 version used by Tycho 1.2.

@Mickael can you comment?

Not sure what "installable feature" means in this context.


On 05.06.18, 17:10, "tycho-user-***@eclipse.org on behalf of Brian de Alwis" <tycho-user-***@eclipse.org on behalf of ***@gmail.com> wrote:

What are the impacts of generating a.jre.javase=10.0.0? Does it only affect products, or does it affect installable features too?

Looking forward to moving to JUnit5!

Tycho 1.2.0 has been released and should soon be available from maven central.
See the release notes [1] for details of enhancements and bug fixes in this release.
Thanks to
Jonah Graham
Mat Booth
who contributed patches for this release.
And thanks and to everyone who helped us with testing the staged version.
Tycho team
[1] http://wiki.eclipse.org/Tycho/Release_Notes/1.2
tycho-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
tycho-user mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Mickael Istria
2018-06-06 07:03:36 UTC
Hi all,

TL;DR: it only affects products.

Jan is right.

Products built with Tycho 1.2 will NOT have direct dependency to
a.jre.javase/x.y.z but have a dependency to capability JavaSE/x.y.z; and
Tycho 1.2 includes by default with product build a.jre.javase that contains
all JavaSE/x.y.z known at the date of the build. So the compatibility is
For "older" products that are *consumed* with Tycho 1.2 but were built
before Tycho 1.2 (and before Photon M7), then the product would still have
the requirement to exact a.jre.javase/x.y.z which is different from the one
added automatically by Tycho 1.2. Even before 1.2, this unit has between
usually and always been included in the same repository as the product
(this from the inception of Tycho), so if your TP contains the product, it
most likely also contain the matching a.jre.javase unit, and you should get
no problem. In some cases (slicer .target files I believe), when migrating
to Tycho, one may need to explicitly add the a.jre.javase to the TP if it's
not already done.

Features never had a requirement on a.jre.javase nor on some JavaSE by
default. That didn't change. So feature are not impacted at all by this

Bundles now add a JavaSE/x.y.z requirement according to their BREE. Tycho
has about always added the necessary a.jre.javase unit to the resolver for
each bundle, even before the JavaSE became a expressed as a p2 requirement.
So not much did change here: Tycho still adds the necessary unit according
to BREE, and the bundle resolve fine against those.


Continue reading on narkive: