We use maven artifacts with custom extension and type, but both with different names. So extension for example is "projlib" and type is "tib-projlib".

The detection of upstream and downstream jobs does not work properly for theses types of projects. Therefore I created a hotfix commit in https://github.com/smueller18/pipeline-maven-plugin/commit/16f1d03e8b4a338e7304fefe8e027ab8b428a080 that our dependency chain works properly.

Here is the correct chain of upstream and downstream jobs (by using the hotfix):

And here is the output without my hotfix:

The dependencies are recorded correctly, but the linking to the jobs is not. As you can see in the attached maven spy logs, the id is recorded as "de.filiadata.soa.tibco.bw.intf.afv.stibafv001-intf:stibafv001-intf-library:tib-projlib:1.0.0-SNAPSHOT" for the interface project, but in the dependency list, the "tib-" is missing ("de.filiadata.soa.tibco.bw.intf.afv.stibafv001-intf:stibafv001-intf-library:projlib:1.0.0-SNAPSHOT").