Maven parent with dependencyManagement using property, property override in child should trigger updates

[wleese]

Tell us more.

From #46469

I have an app with a pom.xml that has a parent.

The parent defines dependencyManagement and uses a variable for the version, like so:

<properties>
    <jackson-bom.version>3.1.0</jackson-bom.version>
</properties>

<dependencyManagement>
<dependency>
  <groupId>tools.jackson</groupId>
  <artifactId>jackson-bom</artifactId>
  <version>${jackson-bom.version}</version>
  <type>pom</type>
  <scope>import</scope>
</dependency>
</dependencyManagement>

The parent in this case is a public, well known dependency spring-boot-dependencies.
The parent is confirmed to be available (downloadable by mvn(w) and renovate).

In my app pom.xml I override the property with a newer version - newer, but not the latest:

<properties>
    <jackson-bom.version>3.1.5</jackson-bom.version>
</properties>

Looking at my Dependency Dashboard, I see that the dependency is not detected.
Only when I add that same dependencyManagement snippet from the parent, into my app pom.xml, does Renovate detect the update.

As you can see, in this specific case, this is a "bom import" (type=pom, scope=import).

This situation was previous described as hitting:

maven manager only resolves poms that exist in the repo (via relativePath); it doesn't fetch remote parents like spring-boot-dependencies. So the jackson-bom import in the parent is never seen, and your jackson-bom.version override isn't tied to any dependency. That's why adding the import to your own pom makes it work.

This is a request for supporting remote parent resolution to allow this situation to trigger new dependency updates.