com.google.protobuf.util.Timestamps deprecations refer to unavailable JavaTimeConversions type #18925
Assignees
Labels
Comments
anandolee
added
kotlin
and removed
untriaged
copybara-service bot
pushed a commit
that referenced
this issue
Oct 28, 2024
…etween that we do not yet have alternatives to. Fixes #18925 PiperOrigin-RevId: 690740842
copybara-service bot
pushed a commit
that referenced
this issue
Oct 29, 2024
…etween that we do not yet have alternatives to. Fixes #18925 PiperOrigin-RevId: 690740842
|
Thanks for reporting this issue! I submitted a change to remove those deprecation warnings. |
deannagarcia
added a commit
to deannagarcia/protobuf
that referenced
this issue
Oct 31, 2024
…etween that we do not yet have alternatives to. Fixes protocolbuffers#18925 PiperOrigin-RevId: 691117251
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of protobuf and what language are you using?
Version: 4.27.4 via
com.google.protobuf:protobuf-java-utilMaven artifactLanguage: Kotlin JVM
What operating system (Linux, Windows, ...) and version?
Linux (Debian Bookworm)
What runtime / compiler are you using (e.g., python version or gcc version)
Kotlin 2 + JDK 17
What did you do?
Steps to reproduce the behavior:
com.google.protobuf.util.Timestamps.addWhat did you expect to see
Either
JavaTimeConversionstype is availableWhat did you see instead?
A deprecation warning referencing an unavailable type.
Anything else we should know about your project / environment
There are some
MOEcomments that make it seem like the deprecation annotation and documentation were supposed to be stripped from the open source release.The text was updated successfully, but these errors were encountered: