|
+1 from me for RT PMC
Sorry for the resend, my previous response only went to orbit-dev
Tom
From: orbit-dev <orbit-dev-bounces@xxxxxxxxxxx> on behalf of Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
Sent: Wednesday, January 18, 2023 1:45 PM
To: Runtime Project PMC mailing list <rt-pmc@xxxxxxxxxxx>
Cc: Orbit Developer discussion <orbit-dev@xxxxxxxxxxx>; EMO EMO <emo@xxxxxxxxxxxxxxxxxxxxxx>; ebr-dev@xxxxxxxxxxx <ebr-dev@xxxxxxxxxxx>
Subject: [EXTERNAL] Re: [orbit-dev] Retiring EBR
Dear RT PMC, After discussion with EMO and Orbit here is the proposal: We'll combine a restructuring review that moves the resources for EBR to Eclipse Orbit and a termination review for EBR. Orbit would like to continue using the EBR Maven
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Dear RT PMC,
After discussion with EMO and Orbit here is the proposal:
We'll combine a restructuring review that moves the resources for EBR to Eclipse Orbit and a termination review for EBR. Orbit would like to continue using the EBR Maven plug-in.
Appreciate your +1 to move forward.
-Gunnar
On Jan 11, 2023, at 18:18, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:
Hi everyone,
When EBR was created many years ago there was a huge demand for OSGi bundles. The EBR project came up with a solution to make Maven artifacts easily consumable from p2-enabled OSGi applications. However, it never really fulfilled the role of becoming a
rich source for recipes. Today the primary customer of EBR is Orbit and Eclipse (via Orbit).
In the last year, Eclipse PDE and Tycho made significant progress towards consuming Maven artifacts directly in target platforms. I've looked at the features available and started adopting that in a few projects. I think the technology is ready to make
EBR obsolete.
Therefor, I am proposing to sunset the EBR project. Thoughts? Comments?
|
