Re: [epp-dev] Packaging and shipping runtimes (OpenJ9) as p2 untils in E

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

As for the technical side, isn't it a matter
of getting OpenJ9 or OpenJDK

OpenJ9 only was approved.

Let me clarify.
The approved runtime is OpenJDK libraries + OpenJ9. OpenJDK + Hotspot is
not part of the approval.

Dani



From:
       Mickael
Istria <mistria@xxxxxxxxxx>
To:
       Eclipse
Packaging Project <epp-dev@xxxxxxxxxxx>
Date:
       14.06.2018
13:50
Subject:
       Re:
[epp-dev] Packaging and shipping runtimes (OpenJ9) as p2 untils in EPP?
Sent
by:        epp-dev-bounces@xxxxxxxxxxx

---

On Thu, Jun 14, 2018 at 12:17 PM, Gunnar
Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
wrote:

I think it would. The questions remains, if we want to offer multiple variations of each package - with or without a runtime?

It depends on the package and the target
audience. But I don't think it's something that needs to be addressed right
now. Let's first have something working and then we'll be in a better position
to find out what's the best approach is regarding when to include runtimes
or not.

As for the technical side, isn't it a matter of getting OpenJ9 or OpenJDK

OpenJ9 only was approved.

provisioned on the build machine and flipping the include-launcher flag in the product definition? So the majority of the work would be around build infrastructure?

Would this allow updates of runtime only?
The cool thing if we have the runtime
as p2 units built separately and made available independently of product
is that:
* other projects/RCP could easily reuse
it
* It allows to put in the IDE a link
to the repo containing the "latest" runtime, allowing for example
to provide updates very easily in case we need for instance to deliver
a quick security patch fixed in the runtime.

_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/epp-dev