-
Notifications
You must be signed in to change notification settings - Fork 583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to scala-parser-combinators 2.1.1 #287
base: develop
Are you sure you want to change the base?
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #287 +/- ##
===========================================
- Coverage 49.49% 49.49% -0.01%
===========================================
Files 280 280
Lines 15809 15809
Branches 1005 1051 +46
===========================================
- Hits 7825 7824 -1
- Misses 7984 7985 +1
Continue to review full report at Codecov.
|
Hi @xerial , thanks for the PR! We usually keep all our repositories at the same version of 3rdparty dependencies, and during the tests, we found some issues in other repositories (Scrooge and Finatra), so this would take longer than expected. |
Just wanted to mention that this update is also necessary for the Scala3 migration in general (see #290 where I had to include it as well). 🙂 |
ok. I'll rebase this PR onto develop |
6fbb23c
to
774fd78
Compare
It's been already rebased. @pjfanning |
Problem
Use scala-parser-combinator
2.0.02.1.1, which is compatible for Scala 2.11 - Scala 3.0.0.If a project using twitter-util has a dependency to scala-parser-combinator 2.0.0 with sbt 1.5.x, an error like this will be shown:
Related article: https://www.scala-lang.org/blog/2021/02/16/preventing-version-conflicts-with-versionscheme.html
Solution
Upgrade the scala-parser-combinator version of twitter/util or adding this setting to build.sbt:
Result
There should be no behavior change with this upgrade.