| Re: [orbit-dev] Retiring EBR |
Hi,one question, what to do with projects that are just refusing to add proper OSGi manifest entries?like Apache HttpClient (for now...)
then we can't consume them through pure maven right?Also maven artifacts are for the most parts never signed, i know there is now a different kind of thing you can use. but i looked at it and it is very hard to setup correctly (if you aks me...)It just is not that simple then having a keystore in a private git repo that the build server but also all the developers that now and then need to build the product them self can use.. (over multiply platforms like Mac (x86 or M1), Linux and Windows)johan_______________________________________________On Wed, 11 Jan 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?
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/orbit-dev
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/orbit-dev