If there are multiple jobs building the same maven module, currently it's more or less random which of these jobs is included in Jenkins' dependency graph.
The mechanism should be improved to choose the more relevant jobs - if possible - and the deliver predictable results.
I've implemented a prototype here:
|Field||Original Value||New Value|
|Assignee||kutzi [ kutzi ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Component/s||maven-plugin [ 16033 ]|
|Component/s||maven2 [ 15487 ]|