I noticed that Jenkins marks the wrong module as failed in a multi module Maven build when using the parallel mode of Maven (-T >1).
What I mean is that the module view of a build does not show the same result as the maven log output. So when ModuleA fails according to the summarized log of a build (which is usually right) Jenkins marks another module (ModuleB) as failed. Additionally the logs of the modules are screwed up (contain log output from other modules) and do not show information concerning the reason for the fail (but I think that's another issue).

If I have some time, I'll analyze this further and try to create a sample project where this is replicable. I think it might be connected to the last finished module of a parallel build (if ModuleA and B are built at the the same time, ModuleA fails and ModuleB finishes after the failed ModuleA, ModuleB is shown as the failed module... but that's just a hunch).

This is clearly no showstopper but it annoys the heck out of me to always analyze the summarized log of the build to see what broke the build (and also explain this to other developers who are confused by the fact that the overview does not show the failing module).