On 11/03/2017 02:13 PM, Giovanni Mascellani wrote: > version 5.0.3, which I hope to upload as soon as possible, will > implicitly solve this bug, because is drops the distinction between the > two artifacts (and it adopts only Apache-2.0). I see no point in adding > compatibility POMs, because the groupId and artifactId are changing > anyway, so it is better to directly divert reverse dependencies to these.
Great, I like simplifications :) Note that you can use the --relocate parameter in debian/<package>.poms to redirect the old Maven groupId/artifactId to the new ones. This will avoid updating most of the reverse dependencies (at least the Maven based packages, Gradle doesn't support relocations). Emmanuel Bourg
