Resolves #474: Add property support to UseDepVersion

[andrzejj0]

• adding a new parameter, processProperties, which will also update property values if dependencies are controlled by properties
• the above parameter will be turned off in order to retain backwards compatibility

The behaviour of the property is described here:

/**
 * <p>Will augment normal processing by, if a dependency value is set using a property, trying to update
 * the value of the property.</p>
 * <p>If the property value is specified directly, will process it normally (as with {@code processProperties} being
 * {@code false}. If the property being updated is redefined in the reactor tree, will only change the property
 * value which lies closest to the dependency being updated. If the same property is also used to set
 * the value of another dependency, will not update that property value, and log a warning instead.
 * Finally, if the property value is specified in a parent file which is outside of the project, will log
 * a warning message.</p>
 * <p>Default is {@code false}.</p>
 *
 * @since 2.14.2
 */

also, the behaviour is also "described" in the unit tests.

@slawekjaranowski please review

By the way, I've put 2.14.2 tentatively, but because of the nature of this PR, I'd understand if it did not fit into the release.

[andrzejj0]

Manual testing...

[andrzejj0]

Changed it so that it doesn't scan the whole tree if we're not processing properties.

Unfortunately, there's one problem I still don't know how to tackle -- maven unnecessarily descends into children even if the plugin could have made all necessary changes starting from root level.

Do you know how to change that so that Maven doesn't run recursively -- from the plugin?

[slawekjaranowski]

I would like to postpone this for next minor release ... in next year 😄

[andrzejj0]

That's OK 😄

[andrzejj0]

So I guess that's a nice PR for 🎄😄

[andrzejj0]

Note to self: https://maven.apache.org/developers/mojo-api-specification.html#The_Descriptor_and_Annotations

Since there's time, I'll polish it a bit.

[andrzejj0]

Changed to aggregate mode; this change spurred the creation of a new enhancement: #880

[andrzejj0]

Temporarily converting to draft: let's see if I we can use maven (to do the recursion) and plugin context instead.

Nope, it would make things much simpler, but -- unfortunately, the modules seem to be built in the wrong order - from top to down.