Thanks Alexander for pointing me to the pre-reqs target and for logging the bug!
I see that the pre-reqs target is getting the bundles from Orbit, so that answers that part of my question
If I understand correctly, all that will be needed for 4.17 M1 will be to bump the version in platform pre-reqs target.
I wonder if a good practice would be to review the platform pre-reqs target anytime new bundle versions are added to Orbit.
It seems that platform should use the latest versions when possible.
Maybe this check could even be automated, but I’m not sure of the right place to do this.
From: <cross-project-issues-dev-bounces@xxxxxxxxxxx> on behalf of Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
Reply-To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: Friday, June 12, 2020 at 11:41 PM
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Subject: Re: [cross-project-issues-dev] feature dependency version incompatibility
Shouldn’t third-party dependencies be resolved from Orbit instead of from the updates repo?
How do I update one of these dependencies that is being provided by the updates repo, such as javax.annotation?
Unfortunately there is no other way I'm aware of other than rebuilding eclipse platform after changing the prereqs target file.
In any case, it seems that it must be too late to fix this for 2020-06, but these should get reconciled before 2020-09.
I’m interested in helping with this work, but I’ll need the information I asked for above and could use some direction about which project to log the bug in for tracking.
P.S. Is this an appropriate discussion for cross-project-issues dev? I don’t want to spam the list so please let me know if this is off-topic and how I should communicate instead.
cross-project-issues-dev mailing list
To unsubscribe from this list, visit