Currently the Migration Tool only has a scala api which requires the java user to convert the results (scala futures), which is not very convenient.
It was recommended to introduce a scaladsl and javadsl package, and then to move the existing scala based implementation one to scaladsl packed and then create a subclass (or facade) where it currently resides with the same name, and deprecate that.
Constructor signature should be maintained to stay binary compatible, if possible.
Currently the Migration Tool only has a scala api which requires the java user to convert the results (scala futures), which is not very convenient.
It was recommended to introduce a
scaladslandjavadslpackage, and then to move the existing scala based implementation one toscaladslpacked and then create a subclass (or facade) where it currently resides with the same name, and deprecate that.Constructor signature should be maintained to stay binary compatible, if possible.