-
Notifications
You must be signed in to change notification settings - Fork 78
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
Problem with HibernateJpaConfiguration after migrating from com.sun.xml.bind:jaxb-impl to org.glassfish.jaxb:jaxb-runtime #606
Comments
Hi @rcsilva83 , welcome back! The change made here might be spread across multiple repositories: We'd need to figure out if there's a missing parallel change to be made in rewrite-hibernate, or whether there's more to the one to one replacement that's done currently. Any help appreciated as I lack a bit of detail on which version of Hibernate you're using, as the HibernateJpaConfiguration class for v3.3.x itself does not refer to |
Hi, @timtebeek ! I tracked this problem and it isn't related to HibernateJpaConfiguration but to Jackson. We use some Jackson annotations on some The problem is that, after running the I found some recipes that do this change:
Given that, is there any way to tell OpenRewrite not to run that recipes or to ignore that dependency and leave it as it is? |
Thanks for diving in! The most convenient way to customizing an existing composite recipe is through the recipe builder at https://app.moderne.io/. We're working on getting that integrated into docs.openrewrite.org now that it's using Docusaurus, but that might take a while longer. That said; looking at the changes I wonder if instead of removing recipes we should be adding a migration step instead:
With a change dependency to go from |
Actually, these dependencies are being pulled by external packages we depend on and they aren't update yet, unfortunately... I think, for my use case, it is better to make a new recipe using UpgradeSpringBoot_3_3 and then add javax.xml.bind:jaxb-api dependency. This way, we wouldn't need to maintain a custom UpgradeSpringBoot_3_3 recipe and having to manually update it, which seams a lot of work... On the long term, don't you think this kind of change is a bit intrusive to make? I think situations like this, where the developer don't have full control on the migration to In this case, I see 2 solutions:
|
What version of OpenRewrite are you using?
I am using
How are you running OpenRewrite?
I am using the Maven plugin, and my project is a single module project.
What is the smallest, simplest way to reproduce the problem?
What did you expect to see?
No change.
What did you see instead?
What is the full stack trace of any errors you encountered?
Are you interested in contributing a fix to OpenRewrite?
Yes
The text was updated successfully, but these errors were encountered: