Hi Alexander, I guess you are right, a wider version range would be acceptable, here. I widened the range and created a new build. A patch for Simrel with a reenabled MPC could be found here: https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/170539 Seems to work. Please, review the changes and accept if everything is okay.
Leif Geiger Product Manager & Software Engineer -- +49 (0)69 2475666-22 | leif.gei...@yatta.de<mailto:leif.gei...@yatta.de> | www.yatta.de<http://www.yatta.de/> Yatta Solutions GmbH · Mainzer Landstraße 50 · 60325 Frankfurt a.M. (Germany) Registered Seat: AG Kassel, HRB 14720 · VAT-ID DE263191529 · Managing Director Johannes Jacop From: cross-project-issues-dev-boun...@eclipse.org <cross-project-issues-dev-boun...@eclipse.org> On Behalf Of Aleksandar Kurtakov Sent: Friday, October 9, 2020 8:44 AM To: wa...@eclipse.org; Carsten Reckord <reck...@yatta.de>; Leif Geiger <leif.gei...@yatta.de>; issues, Cross <cross-project-issues-dev@eclipse.org> Subject: [cross-project-issues-dev] MPC disabled in Simrel to contribute Eclipse Platform 4.18 M1 Hi, In order to contribute latest Eclipse Platform to Simrel for 2020-12 M1 I had to disable MPC due to failing to resolve [1] due to too tiny dependency version range. There is a fix in mpc git [2] which should fix the immediate issue but IMHO is not the correct one long term. The recommended way should be to bump the range to [1.0.0,2.0.0) instead. [1] https://ci.eclipse.org/simrel/job/simrel.runaggregator.VALIDATE.gerrit/1732/console [2] https://git.eclipse.org/c/mpc/org.eclipse.epp.mpc.git/commit/?id=08179882adf4898c47aedfbc69b9ee4a75775f66 -- Alexander Kurtakov Red Hat Eclipse Team
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
