The child.inherit.append.path attribute introduced with
MNG-5951 unfortunately does not support the use case where the children of the element with the attribute should follow different inheritance rules. Take a typical configuration for Github, for example (taken from <http://central.sonatype.org/pages/requirements.html>):
If the ossrh-demo.git repository contains a child module called some-module, then that child’s scm/url should become http://github.com/simpligility/ossrh-demo/tree/master/some-module as per the normal inheritance rules, but both the scm/connection and scm/developerConnection URLs should remain unchanged.
Unfortunately, this is not possible with child.inherit.append.path, which acts on all children simultaneously.
IMHO, this is a conceptual problem. In particular, setting child.inherit.append.path on the root element to just control a single child (project/url) feels wrong, as the attribute is in all likelihood not even located close to the <url> element it controls.