-
Notifications
You must be signed in to change notification settings - Fork 4
Remove bundles that have OSGi metadata upstream #25
Comments
I will be adding to the description of this issue a check-list covering all the items we plan on removing. |
In the first instance I will be pruning out all the items listed in the target platforms for the projects consuming from maven central and contributing to simrel already, such as platform, tm4e, etc. See https://github.com/eclipse-oomph/oomph.incubator/tree/master/maven/org.eclipse.oomph.maven.generator/report for the source that I am using. |
Part of eclipse-orbit#25 Fixes eclipse-orbit#9
The contents of this bundle was actually jakarata.annotation 1.3.5 Part of eclipse-orbit#25
For some reason with JNA the old versions did not get deleted as we went along. The Eclipse Platform is using/shipping 5.13 which is newer than any of the versions in Orbit Part of eclipse-orbit#25
Part of eclipse-orbit#25
For now JNA 4.5.1 is kept because it is needed by httpclient4 which is still used by many consumers (ECF, Mylyn, User Storage) Eclipse Platform is already using 5.13 which is newer than latest in Orbit Part of eclipse-orbit#25
For now JNA 4.5.1 is kept because it is needed by httpclient4 which is still used by many consumers (ECF, Mylyn, User Storage) Eclipse Platform is already using 5.13 which is newer than latest in Orbit Part of eclipse-orbit#25
For now JNA 4.5.1 is kept because it is needed by httpclient4 which is still used by many consumers (ECF, Mylyn, User Storage) Eclipse Platform is already using 5.13 which is newer than latest in Orbit Part of #25
Instead I will do the new work on a branch as I hadn't realized that the new simrel-orbit was consuming the I-builds and projects such as xtext are consuming simrel-orbit already. Part of eclipse-orbit#25
|
We can remove all of com.github.jrn.* from Orbit See this for analysis: eclipse-linuxtools/org.eclipse.linuxtools#213 The two that need wrapping are handled here: The rest that don't are here: |
FYI, I am creating a rather long list of exclusion rules, which is still a work in progress: |
Xtext uses classgraph |
What is "classgraph"? |
I believe that's the one, yes. |
yes this is classgraph. it has osgi metadata as it looks like so we could update. btw. with the guice 7 bump the guice thing is done. so is it about others depending on old guices? |
Rather than handling it by removing bundles from EBR style Orbit (this repo) the new Orbit aggregation repo is excluding old bundles as they are replaced - see https://github.com/eclipse-orbit/orbit-simrel/blob/main/orbit-aggregation/orbit.aggr |
For a long time Orbit's re-bundling was the way to get third-party libraries from Maven into an Eclipse p2 consumable state.
For a while now there has been a better way for getting third-party dependencies that already contains OSGi metadata. That is to use the M2E's maven target locations and sign the bundles with PGP instead of jarsigning. There has been much communication on mailing lists and in issues on this topic in the the last couple of years.
The next step now is to stop maintaining the Orbit bundles that rewrite the OSGi metadata when the upstream bundle has the OSGi metadata in it correctly already.
The goal is to have the first step of this process done for 2023-09 M1 by removing the bundles. In addition @merks's work in https://github.com/eclipse-oomph/oomph.incubator will be migrated into the Orbit project so that Orbit provides p2 repos with the PGP signed third-party dependencies already in them.
Here are the bundles that have valid OSGi metadata in the upstream version that we plan to remove. This list will be added to as we vet additional bundles.
The text was updated successfully, but these errors were encountered: