Closed merks closed 1 week ago
Frankly, I'm not a fan of simulating "activity" of a bundle with no active maintenance for some time already.
To remove the dependency in our test bundles I just filed #3029 - after that it should be safe to stop building the bundle altogether.
To remove the dependency in our test bundles I just filed #3029 - after that it should be safe to stop building the bundle altogether.
After resolving #3029 only these locations still reference to org.eclipse.jdt.annotation_v1:
FYI, both appear to have new qualifiers and hence both have new signatures:
But only one has a new minor version so only one will be published to Maven Central for the upcoming release...
After resolving https://github.com/eclipse-jdt/eclipse.jdt.core/issues/3029 only these locations still reference to org.eclipse.jdt.annotation_v1:
- org.eclipse.jdt.ui.tests: MANIFEST.MF
https://github.com/eclipse-jdt/eclipse.jdt.ui/pull/1712 is stuck with seemingly unrelated test failure. merged.
After resolving #3029 only these locations still reference to org.eclipse.jdt.annotation_v1:
- ...
- the JDT feature
this is eclipse-jdt/eclipse.jdt#118
merged.
Let's see if the next build still contains any traces of the 1.x version.
Let's see if the next build still contains any traces of the 1.x version.
I don't see it any more. Closing this PR.
https://github.com/eclipse-jdt/eclipse.jdt.core/issues/3027