|Re: [cross-project-issues-dev] feature dependency version incompatibility|
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.
On Sat, Jun 13, 2020 at 8:57 AM Homer, Tony <tony.homer@xxxxxxxxx> wrote:
Eclipse Platform build using https://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target where versions are strictly fixed as updates are not always straightforward when done on the lowest level in the stack.
Unfortunately there is no other way I'm aware of other than rebuilding eclipse platform after changing the prereqs target file.
I'm here with you and have opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=564264 to track it down. As the bundle is in Orbit already (thanks!) this shouldn't be an issue to be done for 4.17 M1.
Red Hat Eclipse Team
Back to the top