Skip to content
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

Feature/update kryo #838

Merged
merged 7 commits into from
May 28, 2021
Merged

Feature/update kryo #838

merged 7 commits into from
May 28, 2021

Conversation

martin-v
Copy link
Member

@martin-v martin-v commented Mar 5, 2021

  • the code follows the Clean Code guidelines.
  • the necessary tests are either created or updated.
  • all status checks (Travis CI, SonarCloud, etc.) pass.
  • your commit history is cleaned up.
  • you updated the changelog.
  • you updated necessary documentation within retest/docs.

Description

Update kryo to new major version.

State of this PR

Don't fixes #836, but there are first steps in implementing it.
But still PR can be merged, because the unfinished code for #836 should not cause any harm.

@martin-v martin-v requested a review from dkrn03 March 5, 2021 16:45
@cla-bot cla-bot bot added the cla-signed label Mar 5, 2021
@rebazer rebazer force-pushed the feature/update-kryo branch from a4da99a to ab15d55 Compare March 5, 2021 16:46
@martin-v martin-v force-pushed the feature/update-kryo branch from ab15d55 to 51434f6 Compare May 28, 2021 12:10
@rebazer rebazer force-pushed the feature/update-kryo branch from bab4b46 to fdd735a Compare May 28, 2021 12:33
@mergify mergify bot merged commit 40f78b2 into develop May 28, 2021
@mergify mergify bot deleted the feature/update-kryo branch May 28, 2021 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

We should use kryo.setRegistrationRequired( true )
2 participants