Add a new recipe to migrate to io.hypersistence:hypersistence-utils-hibernate:6 types

[iuliiasobolevska]

What problem are you trying to solve?

What precondition(s) should be checked before applying this recipe?

Should use io.hypersistence:hypersistence-utils-hibernate-60 or io.hypersistence:hypersistence-utils-hibernate-62.
Note: I logged a separate issue for package group changes: #4 since that one is trivial to do and requires fewer things to be considered.

Describe the situation before applying the recipe

From https://github.com/vladmihalcea/hypersistence-utils#hibernate-5:

@Type(type = "json")
private Map<String, String> properties = new HashMap<>();

Describe the situation after applying the recipe

From https://github.com/vladmihalcea/hypersistence-utils#hibernate-6:

@Type(JsonType.class)
private Map<String, String> properties = new HashMap<>();

Any additional context

We used to also apply

@TypeDefs({@TypeDef(name = "json", typeClass = JsonStringType.class)})

at the class level. If I read migration guide correctly these annotations should be removed by the recipe.

[timtebeek]

Thanks again for the clear before/after description and helpful links to the documentation! As opposed to #4 this change would indeed require a custom recipe and visitor, but not a particular tough one to implement I think.

I'd invite anyone that wants to pick this up to start with a couple unit tests to capture the before and after situation you've described above, and open a draft pull request to kick start development. Even if you're unsure whether you'd be able to complete the recipe, it's a good way to work towards a solution.

In time, if we develop more custom hibernate migration recipes we might even consider starting a separate rewrite-hibernate repository, and invite people like Vlad to contribute recipes to migrate their users over the newer versions.