Fix Package Tangles

[garyrussell]

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 and DefaultConfiguringBeanFactoryPostProcessor has references to ...json. Moving the converter and property accessor to ...config should solve it, but doesn't feel right.

[artembilan]

Another way to fix the first one is to move JavaUtils to the top-level package.
This class is indeed has nothing to do with any infrastructure to be in the specific package. At the same time being in the top-level package it sets free our hands to use it from anywhere.
Another possible fix is to remove its usage from that new IntegrationProperties 😄 .

The second problem is probably easier to fix removing that @IntegrationConverter from the JsonNodeWrapperToJsonNodeConverter and register it into the target GenericConversionService some other way.

[garyrussell]

[garyrussell]

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 core is a special case.

[artembilan]

Perhaps the IntegrationReactiveUtils has to go to that core then...

Those MessageSource, MessageProducer, MessageSelector etc. I feel better would live in the root package.
Or... Those ErrorMessagePublisher and MessagingTemplate are in the wrong place since they depend on support package and so on down to util.