Since JENKINS-44721, pipeline jobs have the ability to be triggered by other pipeline jobs when one of their SNAPSHOT dependencies changes. While this works well already, there is a use case which was supported in the old Maven project type which is not supported any more, and that is the triggering when the parent of an artifact changes. An example scenario would be as follows:

Jenkins project A builds Maven modules a0, a1, a2, and so on. a0 is the parent POM of all a* modules.

Jenkins project B builds Maven modules b0, b1, b2, and so on. b0 is the parent POM of all b* modules. b0 uses a2 as its parent POM.

In the old Maven project, a dependency between A and B would have been established because of the parent dependency between b0 and a2. With the pipeline-maven-plugin, this is currently not the case, so a build of A does not trigger a new build of B.

This behavior could probably be recreated by reading the parent artifact from the POM and declaring it as additional dependency.