| Re: [epp-dev] Update to 2020-09 installs the JustJ JRE |
Mickael,
Yes, and no. The point is that in this case too, a JustJ JRE was installed via update, and that JRE behaves differently that than system JRE/JDK. The embedded JRE does have cacerts, but only the ones shipped with that JRE, not cacerts located elsewhere on the system.
And note that when reproducing this problem over the weekend, I
created a JEE installation (2020-03 and 2020-06) with Java 11.0.5
explicitly as the -vm parameter and when updating those
installations to 2020-09, the JustJ JRE 14.0.2 was installed and
the -vm parameter was changed accordingly.
Regards,
Ed
Hi Ed,
Just to make sure, the cacerts and the update issues are *not* related, are they?
On Mon, Oct 12, 2020 at 9:35 AM Ed Merks <ed.merks@xxxxxxxxx> wrote:
FYI,
This bug describes the problem mentioned in the title of this email:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=567504
The problem was also noticed here:
https://www.eclipse.org/forums/index.php/mv/msg/1105521/1833352/#msg_1833352
I was able to reproduce this as well, i.e., install (with the installer)
the 2020-06 (or 2020-03) JEE package, and then check for updates. After
the updates the JustJ JRE plugin and fragment are installed, but not the
feature, so the user has no possibility to opt out nor to uninstall it.
This is unexpected p2 behavior because there are no explicit
requirements on the JRE plugins, so either the EE capabilities or the
java.package capabilities of the JRE plugin are being resolved
preferentially over the available alternatives.
I suppose one way to fix this is to not include the JREs in the EPP p2
repo...
Regards,
Ed
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/epp-dev
--
_______________________________________________ epp-dev mailing list epp-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/epp-dev