-
Notifications
You must be signed in to change notification settings - Fork 172
upgrade to jackson 2.14.2 #273
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
@mdedetrich any idea how to get the Scala 3 build to ignore deprecation issues? https://github.com/apache/incubator-pekko/actions/runs/4532777359/jobs/7984657231?pr=273 is failing, seems to be because it won't allow deprecated code in the build |
How about adding |
Alternately you can just copy https://github.com/apache/incubator-pekko/pull/270/files#diff-676691b2e85cad6026adb107942b7c9325394e20e015b131fdcebd3b2b7794b0R137 from my Scala 3.3 PR, that will just globally disable any deprecation warnings in the Scala3 build (which we will probably have to do in the future anyways). |
@pjfanning For the latest error from https://github.com/apache/incubator-pekko/actions/runs/4533101420/jobs/7985451216?pr=273 you probably need to add |
@pjfanning Okay so for the new errors in https://github.com/apache/incubator-pekko/actions/runs/4533274521/jobs/7985858691?pr=273 you probably need to port some of the fixes from #270, specifically the |
Thanks @mdedetrich - it looks like I needed all your code changes from your Scala 3.3 PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I am going to approve this PR but since there was some ambivalence about upgrading the Scala version (see #6 and https://lists.apache.org/thread/mk88ybzx51k7x7x102drtbzh6l68k0xm) we should probably check with community that this is broadly okay before merging (as people may already know, personally I am all for updating the Scala 3 version but thats just me)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general, lgtm.
I don't quite see how the general silencing and the @nowarn
and @unchecked
annotation changes play together here. Can we find a way to silence exactly the deprecation warnings we are concerned about and only in that submodule?
@@ -134,7 +136,7 @@ object PekkoDisciplinePlugin extends AutoPlugin { | |||
case Some((2, 12)) => | |||
disciplineScalacOptions | |||
case _ => | |||
Nil | |||
Seq("-Wconf:cat=deprecation:s") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does that mean we disable all deprecation warnings for Scala 3 for all submodules. Is that really what we want?
You can also match by other factors, so maybe we can restrict the silencing to Jackson in particular?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To provide some context, this flag is needed for Scala 3.2.x in general, not Jackson specifically. It appears there was an issue in Scala 3.1.x where it wasn't reporting deprecations as it should and this was fixed in Scala 3.2. I also had to the do the same fix in the PR I created that only updates to Scala 3.3 (with no other changes), see https://github.com/apache/incubator-pekko/pull/270/files#diff-676691b2e85cad6026adb107942b7c9325394e20e015b131fdcebd3b2b7794b0R137.
actor-typed-tests/src/test/scala/docs/org/apache/pekko/typed/InteractionPatternsSpec.scala
Outdated
Show resolved
Hide resolved
@jrudolph So the changes here were copied from my work in Scala 3.3 (see #270) because it turns out all of the Scala 3 specific changes done in the Scala 3.3 PR due to Scala 3 update was actually added in Scala 3.2 (which this PR is updating to). With the deprecation warnings, there was a lot of places that Scala 3.2/3.3 was warning about deprecation so at least in my Scala 3.3 PR I made the decision to add the flag in order to reduce noise. While it was possible to use the Regarding |
…nteractionPatternsSpec.scala Co-authored-by: Johannes Rudolph <[email protected]>
@mdedetrich @jrudolph are there further changes needed here or is it safe to proceed with a merge? |
Thanks for the explanation, @mdedetrich. The whole linting business here is quite a mess anyway, so it's ok for me to go ahead. Maybe create a ticket to revisit linting rules for Scala 3 (or overall...). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm
#7
JsonMapper.builder()...
to create a configured MapperBuilder and to create JsonMapper/ObjectMapper instances from it