| Re: [platform-dev] backporting and building? |
|
Hi Jonah- Thanks for the suggestions and clarifications. Yes, I did have the wrong link – I only read the commit message and didn’t notice that the change was only for the tests. After I realized that, I went ahead with my own changes in which I replaced all the instances of ant 1.10.7 with
the 1.10.8.qualifier that is in Orbit for 2020-06. So far I have not succeeded in completing a local build, but I haven’t spent that much time on it, yet. I’m not sure if I should be building with Java 8 or Java 11 – I tried with both and had different problems
with each. >> If you are building your own app, your app probably has its own .target or equivalent in the pom file and in that file you can point at the new orbit (2020-06), along with the older platform (4.15) version. I did try this, pretty much exactly as you suggest in my product’s target, but the exact version of ant is hard-coded in the platform feature, so my build failed: [ERROR] Missing requirement: org.eclipse.platform.feature.group
4.15.0.v20200305-0155 requires 'org.eclipse.equinox.p2.iu; org.apache.ant [1.10.7.v20190926-0324,1.10.7.v20190926-0324]'
but it could not be found Before I go back to attempting a local build, I’m going to try what I understand as Christoph Läubrich’s suggestion to just swap out the version of Ant after the build. I’m not sure if the version requirements get checked at runtime, but
it’s an easy thing to try. Again, thank you for taking the time to respond! Tony Homer From: <platform-dev-bounces@xxxxxxxxxxx> on behalf of Jonah Graham <jonah@xxxxxxxxxxxxxxxx> Hi Tony, I suspect that in your original message you have the wrong link still - that may be the cause of some of the confusion that seems to be in this conversation. The commit you reference is a change only to tests and I assume that you are
not shipping tests nor really need to rerun them as part of your RCP application. The platform change that actually changes the version of Ant that is shipped is
https://git.eclipse.org/r/163228 - along with some earlier updates that point at newer orbit URLs that include the new ant version. If you are building your own app, your app probably has its own .target or equivalent in the pom file and in that file you can point at the new orbit (2020-06), along with the older platform (4.15) version. You may need some version constraints
in your .product file to make sure that only the correct version of ant is included. On to some of your other questions in case you have this or other reasons to rebuild the platform: > Still just wondering if it is expected that such a change would be needed. I think the change is needed as once a version of Eclipse is released its branch is left in a somewhat broken state because the I-build deps are deleted. It may be nice if the branches for completed versions were left in a buildable state,
but that is not a priority for active developers, so someone would have to do that work. Please note that this problem exists whenever you want to build an older version of Eclipse. For example with the multi-repo builds of Eclipse it can be quite hard to
build an old version of Eclipse to, for example, run git bisect to identify a problem. During development lots of old I-builds are left so that you can do that, but once a release is done those are removed. PS. There are other members of the community who have the same underlying issue - ie using, maintaining/supporting older versions of Eclipse platform in their product. See this interesting discussion that Andrey started on this topic (https://www.eclipse.org/lists/platform-dev/msg02171.html)
that resulted in this entry on the wiki (https://wiki.eclipse.org/Platform/How_to_Contribute#Contributing_to_maintenance_release_branches). It seems
you, Andrey and others have similar issues to handle. I hope the above helps. Let me know if I have misunderstood the direction you are aiming for. Jonah ~~~ On Mon, 8 Jun 2020 at 00:19, Christoph Läubrich <laeubi@xxxxxxxxxxxxxx> wrote:
|