+1 to move to 2.13. Last time when we updated to 2.12 we had to update all modules also as the Scala version is specified per module. And those changes had to be coordinated See https://github.com/apache/openwhisk/issues/3952 for link to changes done in various module
Chetan Mehrotra On Thu, Nov 21, 2019 at 12:33 PM Markus Thömmes <[email protected]> wrote: > Am Mi., 20. Nov. 2019 um 19:52 Uhr schrieb David P Grove < > [email protected] > >: > > > > > "Markus Thömmes" <[email protected]> wrote on 11/20/2019 > 10:44:21 > > AM: > > > > > > Hey fellow Openwhiskers, > > > > > > I somewhat fancy a little bit of Scala action and wanted to give > updating > > > Openwhisk to Scala 2.13 a shot. They have reworked quite a bit in Scala > > > 2.13 and keeping track with the versions might be very valuable, > > especially > > > if Dotty comes around eventually. > > > > > > To pull that off, we'll need to bump quite a few libraries, some of > them > > > even in their major version. I plan to send each of those major > upgrades > > as > > > individual PRs, so we can pinpoint potential issues via git bisecting > if > > > necessary. > > .... > > > > > > We'll see if there are more dragons, but I'm happy to work through them > > to > > > some extent :). Is anybody concerned with doing this move in general > and > > > with the process laid out specifically? > > > > > > > Generally sounds good; happy to have someone pushing on chasing language > > versions :) > > > > One thing to be careful of is that many downstream repos (runtime, > > providers) depend on the test suite from the core repo. We had a couple > > rounds of breakage in the last few months where a test suite change got a > > clean core travis run, but still broke all the downstream repos leading > to > > some hasty fixing and/or reverting. > > > > I hear you! Is there a good way to verify stuff works across all > repositories or will I have to manually go through all of them and check if > my changes have any impact? > > > > > > -dave > > >
