| Re: [epp-dev] JustJ JRE for AArch64 |
Wayne,
I was actually hoping that the JustJ JREs did not end up in any
other p2 repository, including not in the EPP repositories; there
is no need for them to be present there.
We've already seen that an update from < 2020-09 caused a
JustJ JRE to be installed simply because it's available in the
2020-09 EPP repo . That's because, as of 2020-09, JDT's IUs
require package imports of Java packages that are not provided by
the "fake" a.jre.javase IUs but rather are provided only by the
JustJ JREs.
Consider too that the IUs are really large and there are many variations of them:
https://download.eclipse.org/justj/jres/15/updates/milestone/S202010270507/index.html
It's not clear up front which consumers want to consume which
variants, so which would I push into the train?
In addition, the JREs release on a schedule that is completely independent of the release train, i.e., whenever there is a new release/update available from the upstream JDK source here:
The installer gives users the option to install a JustJ JRE
directly from JustJ's p2 repositories; this is part of the catalog
information so when a new one is released, it will be available
even in older installers.
And finally, in the end, having older JREs that might potentially have security issues associated with them baked into more p2 repositories just seems like a bad idea in principle.
Regards,
Ed
I'm sure that I just missed a memo somewhere along the way, but is there a reason that Eclipse JustJ, which is a simultaneous release participant, is not in the simultaneous release repository?
Wayne
On Fri, Nov 6, 2020 at 4:40 PM Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
_______________________________________________Thanks Ed.
We are in a brave new world here :-) JustJ (and corrosion) are the first two projects being consumed by EPP without going to simrel. This means the responsibility on pushing out new releases changes hands from the project (JustJ/Corrosion) to EPP itself.
I haven't been paying (enough) attention to the JustJ issue.
@All should we be using Java 15 across the board, or do we need to manage multiple versions. We currently use <url>https://download.eclipse.org/justj/jres/14/updates/release/latest/</url>
ThanksJonah
~~~
On Fri, 6 Nov 2020 at 13:15, Liviu Ionescu <ilg@xxxxxxxxxx> wrote:
> On 6 Nov 2020, at 20:10, Ed Merks <ed.merks@xxxxxxxxx> wrote:
>
> Hi,
>
> It doesn't look like the JustJ Java 15.0.1 JREs made it into the packages for M2. Is there a reason for that?
>
> You folks have asked for a JRE that includes the src.zip (so that source debugging is supported) and there is a JRE for aarch64 for 15.0.1 that you need for the JRE-containing packages. Surely it would be a good idea to test this sooner rather than later.
>
> Note that I don't plan to create a release build for 15.0.1 until it's been validated by an EPP build.
Did I miss some action point? I can test things on my Raspberry Pi OS 64-bit, but for this I need clear instructions on how to do it, since I'm not yet fully mastering the Eclipse Foundation workflows.
Regards,
Liviu
_______________________________________________
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
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
Join us at our virtual event: EclipseCon 2020 - October 20-22
_______________________________________________ epp-dev mailing list epp-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/epp-dev