Always preserve dominant node value (even if empty)

[kwin]

This closes #216

[kwin]

I tested this against the Maven Integration Tests and there were no failures.

[michael-o]

Can you run this change against all Maven Plugin Tools ITs?

[michael-o]

This make sense. Requirement for merge is that MPT are running fine. Waiting for confirmation then I can merge.

[kwin]

Can you run this change against all Maven Plugin Tools ITs?

You mean https://github.com/apache/maven-plugin-tools being build with Prun-its after referencing this PR?

[michael-o]

Can you run this change against all Maven Plugin Tools ITs?

You mean https://github.com/apache/maven-plugin-tools being build with Prun-its after referencing this PR?

Correct, this code must be in use for these ITs.

[michael-o]

@kwin Please rebase against master.

[kwin]

@michael-o Actually this was thought as an alternative to #213 (as this includes blank values), but we can also obviously apply it on top.

[michael-o]

@michael-o Actually this was thought as an alternative to #213 (as this includes blank values), but we can also obviously apply it on top.

I see it as a compliment for #213 therefore a rebase is required.

[sonatype-lift]

⚠️ 22 God Classes were detected by Lift in this project. Visit the Lift web console for more details.

[kwin]

Build is successful with Prun-itsof https://github.com/apache/maven-plugin-tools after upgrading to this version of plexus-utils.
TBH I don't think there is an IT for this config merging behaviour in MPT.