| [mylyn-dev] help with local build |
|
Hi mylyn-dev. My team is working on a fork of Eclipse for C/C++ Developers. The reason we need this is because our company has stringent requirements for releasing software without CVEs. Even if the CVEs are not relevant
to the usage model in the product, we are required to mitigate them. In the case of Eclipse for C/C++ Developers, one of the issues we have to resolve is that Mylyn depends on older versions of Guava. In order to resolve this, we need to build a version
of Mylyn that is updated to use newer versions of Guava. Then we can use our fork of Mylyn to build our fork of Eclipse for C/C++. It’s a pain but as far as I know, it’s our only route forward. We were able to build mylyn-commons, but haven’t been able to build mylyn-contet. I believe this might be because we have our local repositories set up incorrectly, but there are also other issues. For example,
the target file for mylyn.context is pointing at an Orbit repo from 2013, but in looking at ci.mylyn builds for mylyn.context, when the target is being resolved, a 2018 Orbit repo is used. However, grepping the repo for the repo timestamp yields no results.
We read through the docs in the repos and some of the docs in the wiki (https://wiki.eclipse.org/Mylyn,
https://wiki.eclipse.org/Mylyn/Build_Infrastructure,
https://wiki.eclipse.org/index.php?title=Mylyn/Contributor_Reference) and took a look at some of the ci repos but haven’t been able to move forward. We’re going to keep stumbling
along, but could use some help. Specifically, please help us understand how to set up our local clones, any environment variables that are needed and what build command we should use. Our goal is to build a fork of the latest release of
Mylyn including all of the sub-projects. If there is already documentation that explains this and we missed it or misunderstood it, please point us to the exact parts we need to read. Thanks in advance for reading and responding!!! Tony Homer |