-
Notifications
You must be signed in to change notification settings - Fork 313
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
Migrate from Jackson to kotlinx-serialization (KxS) #3904
Labels
Comments
sschuberth
added
on hold
Pull requests that cannot currently be merged
enhancement
Issues that are considered to be enhancements
model
About the data model
labels
Apr 18, 2021
sschuberth
changed the title
Think about migration from Jackson to kotlinx-serialization
Think about migrating from Jackson to kotlinx-serialization
Apr 18, 2021
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
sschuberth
changed the title
Think about migrating from Jackson to kotlinx-serialization
Migrate from Jackson to kotlinx-serialization eventually
Aug 13, 2021
sschuberth
added a commit
that referenced
this issue
Sep 23, 2021
See #3904 for some background information. Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth
added a commit
that referenced
this issue
Sep 24, 2021
See #3904 for some background information. Signed-off-by: Sebastian Schuberth <[email protected]>
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
An interesting article about why not to use Jackson: https://blog.lahteenmaki.net/making-jackson-tolerable.html |
sschuberth
added a commit
that referenced
this issue
May 24, 2023
To avoid both Jackson and kotlinx-serialization annotations on the `SpdxExpression` (sealed) class, simply change the `spdx` property to be a `String`. This is part of #3904. Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth
added a commit
that referenced
this issue
May 24, 2023
To avoid both Jackson and kotlinx-serialization annotations on the `SpdxExpression` (sealed) class, simply change the `spdx` property to be a `String`. This is part of #3904. Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth
added a commit
that referenced
this issue
May 25, 2023
To avoid both Jackson and kotlinx-serialization annotations on the `SpdxExpression` (sealed) class, simply change the `spdx` property to be a `String`. This is part of #3904. Signed-off-by: Sebastian Schuberth <[email protected]>
sschuberth
changed the title
Migrate from Jackson to kotlinx-serialization eventually
Migrate from Jackson to kotlinx-serialization (KxS)
Jul 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Benefits of kotlinx-serialization:
Blockers for the migration to kotlinx-serialization:
No official YAML support; unofficial YAML support is JVM only, so no Kotlin/JSAliases only supported for JSONEdit: Released in version 1.2
No property naming strategies; can we live with camel-case instead of snake-case in ORT result files? (Also see Use camel case instead of snake case for YAML configuration files #5715)Edit: Provide support for JsonNamingStrategy Kotlin/kotlinx.serialization#2111 has been merged 🎉
DotNet / NuGet currently need to deserialize XML, but kotlinx-serialization does not support XML (and probably never will)Current Gradle modules that still depend on Jackson (edited as needed):
The text was updated successfully, but these errors were encountered: