feat: mavenPropertyVersions regexManager

[rombert]

Changes

Adds a new regexManager that can be used for properties defined in pom.xml Maven files.

Context

#21495

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[viceice]

isn't this something the maven manager should support out of the box? 🤔

[rombert]

isn't this something the maven manager should support out of the box? 🤔

Good question. These properties are actually consumed by other plug-ins, which are not visible to the maven dependency manager. Not sure if they could be. Two examples I am aware of:

• pom property at https://github.com/apache/sling-org-apache-sling-starter/blob/ee7eb41337ec4510646d95f1fa951fa8e0b344d0/pom.xml#L51 ; consumed by the the OSGi feature model at https://github.com/apache/sling-org-apache-sling-starter/blob/ee7eb41337ec4510646d95f1fa951fa8e0b344d0/src/main/features/boot.json#L176 . I contributed the osgi manager to renovate, if you think we can make this work in a different way out-of-the-box I can try
• pom property at https://github.com/apache/sling-org-apache-sling-starter/blob/ee7eb41337ec4510646d95f1fa951fa8e0b344d0/pom.xml#L68 ; consumed by the docker-maven-plugin at https://github.com/apache/sling-org-apache-sling-starter/blob/ee7eb41337ec4510646d95f1fa951fa8e0b344d0/pom.xml#L288 ; this could also be extended in case the maven manager starts being aware of other configurations except the "dependency"/"dependencyManagement" ones.

[Churro]

isn't this something the maven manager should support out of the box? 🤔

It does:

renovate/lib/modules/manager/maven/extract.ts

Lines 275 to 287 in 7779ebd

	const propsNode = project.childNamed('properties');
	const props: Record<string, MavenProp> = {};
	if (propsNode?.children) {
	for (const propNode of propsNode.children as XmlElement[]) {
	const key = propNode.name;
	const val = propNode?.val?.trim();
	if (key && val) {
	const fileReplacePosition = propNode.position;
	props[key] = { val, fileReplacePosition, packageFile };
	}
	}
	}
	result.mavenProps = props;

I guess it's really about those special cases @rombert mentioned, where properties are defined but not consumed by dependencies.

[renovate-release]

🎉 This PR is included in version 36.100.0 🎉

The release is available on:

• GitHub release
• 36.100.0

Your semantic-release bot 📦🚀