Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-dev] help with local build
  • From: "Homer, Tony" <tony.homer@xxxxxxxxx>
  • Date: Mon, 16 Sep 2019 16:51:50 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=cuhe75HZGMmff/HDXnuX6LFpCQ3sCKCYD4yz5RcaZ3Q=; b=E0iPH2f/UDZttCV+nxi2JPS5XOJMC6sBjq1L3Mt0POWFYJ2hp/Wk93hdciOXiVQO1Gn6FloMrDcwvYicGE+BrtxSCbFJTbxTchjCSrkpKM5TfQCTgH1i9GIseysqIoJggFm7cBzgwLAnqzXUQX4S7A5w2XoKy73mUfvpZFFpRroyjZfcoJV/Wq+GU2xCKJOInvxCwR7kcQfLotgiUOtiOFzeLbUaMsAVYpe6577mNwTUdB0pJ0ggl5E1hrluhjFi/42BR/sT5+Ngw+nRkrMvEcxaVopXbRqRAisn4K2XE7tNAh6Jnn+GLRmeA8oksg4pukSpyKkBD6IwB+EzcyKVRQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Dp55IiQIR7jU1+ZA7AcDoIXJoqXnw+1tYfZi53vcTqx/L2LCbYSL3Byyyr0KTa8X1KVVCAlmczv7mIzorKRv5YJgMWw9Gl3OOsPBSLR/8E52UpxK8jj5o5X3sjuDBn9Cas6X3pI3ChTPMdVOhhwCEWsWG6SvfGkIUJPIYPgWQuZM5S3VJI2S3B9XwfR9zAzLYCMYBnyjgPyfnjiIeBHfkihfph93D21cU3pxkh53PbgBvTOXYUpeo/wVU6UPkvVVRw19qPMoJCOfEDMIQnPD4gt/tH8PNlGYLngJgqh9iMlEOw44WWzN49m9/LvfvJi2IA8HIV9lvsXCAeU49izSPw==
  • Delivered-to: mylyn-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/mylyn-dev>
  • List-help: <mailto:mylyn-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/mylyn-dev>, <mailto:mylyn-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/mylyn-dev>, <mailto:mylyn-dev-request@eclipse.org?subject=unsubscribe>
  • Thread-index: AQHVbK8IoiECrFNgI0KSZxspAWfXGA==
  • Thread-topic: [mylyn-dev] help with local build
  • User-agent: Microsoft-MacOutlook/10.1d.0.190830

Hi Wim-

 

Thanks for responding.

I do plan to upstream the changes, but unfortunately my product’s development cycle does not align well with the current Eclipse release cycle.

For this reason, I am temporarily forking, then hope to intercept 2019-12 with a change request which will enable me to eventually de-fork.

 

The main change I know of now is to remove the dependency on the older version of guava and switch to a non-vulnerable version.

I believe this has been discussed on cross-project-issues-dev.

 

I did look at ci.mylyn, but it seems like it has some special environment setup that I perhaps am not able to see the configuration for due to permissions?

 

Tony

 

From: <mylyn-dev-bounces@xxxxxxxxxxx> on behalf of Wim Jongman <wimj@xxxxxxxxxxxxx>
Reply-To: Mylyn developer discussions <mylyn-dev@xxxxxxxxxxx>
Date: Friday, September 13, 2019 at 10:12 AM
To: Mylyn developer discussions <mylyn-dev@xxxxxxxxxxx>
Subject: Re: [mylyn-dev] help with local build

 

Hey Tony,

 

We also like software without CVE's. How does forking our software help us? We much rather receive your patches after which you can also expect our help.

 

Did you look at ci.eclipse.org to figure out how mylyn is build?

 

Cheers,

 

Wim

 

 

On Thu, Sep 12, 2019 at 10:24 PM Homer, Tony <tony.homer@xxxxxxxxx> wrote:

Bump

 

From: <mylyn-dev-bounces@xxxxxxxxxxx> on behalf of "Homer, Tony" <tony.homer@xxxxxxxxx>
Reply-To: Mylyn developer discussions <mylyn-dev@xxxxxxxxxxx>
Date: Thursday, September 5, 2019 at 10:41 AM
To: "mylyn-dev@xxxxxxxxxxx" <mylyn-dev@xxxxxxxxxxx>
Subject: [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

_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/mylyn-dev


Back to the top