-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Fix Package Tangles #3656
Comments
Another way to fix the first one is to move The second problem is probably easier to fix removing that |
Actually, the reference "out" of utils (to core) is a bit odd as well - utils are usually "used" by other classes, not vice versa. Although, I suppose |
Perhaps the Those |
Fixes spring-projects#3656 * Move `JavaUtils` from `util` package to the root one to break any possible tangling to/from other packages. * Deprecate an existing `JavaUtils` for backward compatibility * Remove `@IntegrationConverter` from the `JsonNodeWrapperToJsonNodeConverter` and register it manually in the `ConverterRegistrar`. The bean registration for the `JsonNodeWrapperToJsonNodeConverter` must be removed in the next `6.0` * Remove usage of `IntegrationContextUtils` from the `support` package
Fixes #3656 * Move `JavaUtils` from `util` package to the root one to break any possible tangling to/from other packages. * Deprecate an existing `JavaUtils` for backward compatibility * Remove `@IntegrationConverter` from the `JsonNodeWrapperToJsonNodeConverter` and register it manually in the `ConverterRegistrar`. The bean registration for the `JsonNodeWrapperToJsonNodeConverter` must be removed in the next `6.0` * Remove usage of `IntegrationContextUtils` from the `support` package
The first is easy to fix (move
JavaUtils
to...support.util
, then restore/deprecate the class in...util
).The second is not so simple - moving the
JsonNodeWrapperToJsonNodeConverter
to...support.json
doesn't help; the issue is that@IntegrationConverter
is in...config
andDefaultConfiguringBeanFactoryPostProcessor
has references to...json
. Moving the converter and property accessor to...config
should solve it, but doesn't feel right.The text was updated successfully, but these errors were encountered: