Maven shade plugin introduces a feature, enabled by default: [0]. Odlparent picks it up in a regular version bump: [1]. Thus between a "good" merge run console output [2] and a "bad" one [3], the addition is that the bad one shows creation of dependency-reduced-pom.xml file (four times, once for each shaded jar, the scale-util [4] one remains just because it is built last), and maven-install-plugin then prefers taking that (instead of netconf/tools/netconf-testtool/pom.xml [5]) to be the pom the user wants to install as netconf-testtool-2.0.15-SNAPSHOT.pom

[0] -> https://issues.apache.org/jira/browse/MSHADE-36
[1] -> https://git.opendaylight.org/gerrit/c/odlparent/+/100407
[2] -> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/netconf-maven-merge-2.0.x/92/console.log.gz
[3] -> https://s3-logs.opendaylight.org/logs/releng/vex-yul-odl-jenkins-1/netconf-maven-merge-2.0.x/94/console.log.gz
[4] -> https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/netconf/netconf-testtool/3.0.5/netconf-testtool-3.0.5.pom
[5] -> https://github.com/opendaylight/netconf/blob/v3.0.5/netconf/tools/netconf-testtool/pom.xml