Hello  tario , I am Nethra can I take up this issue and try to solve ? 

Sure d_neth04_ go ahead.

tario So I just want to confirm whether I understood the issue properly.
So, with latest version of maven terminal (3.9.0) it doesn't work properly. 
So, can it be fixed if I just change the configuration for the mavin compiler plugin? 
Can I do this by changing it to the version 3.8.7? 

No, this jenkins plugin/the parsing of the console log doesn't work correctly if you use maven 3.9.0 as the console output with the plugin name changes and the logic in the code is depending on the names as were provided by earlier maven versions.

See https://github.com/jenkinsci/analysis-model/blob/master/src/main/java/edu/hm/hafner/analysis/parser/MavenConsoleParser.java where it depends on output of  maven-compiler-plugin, maven-javadoc-plugin and maven-enforcer-plugin and that is now different (e.g. compiler instead of maven-compiler-plugin)

tario  Oh okay, so if I just figure out where inside the above code ( https://github.com/jenkinsci/analysis-model/blob/master/src/main/java/edu/hm/hafner/analysis/parser/MavenConsoleParser.java ) 
the text "maven-compiler-plugin" is being changed to "compiler" then the rest of the logic should work accordingly. And also the code should not depond on that text and give the output with respect to it.
Am I correct?

I was confused about the issue a little, but I tried to make one small change to the MavenConsoleParser.java file in this code https://github.com/jenkinsci/analysis-model/blob/master/src/main/java/edu/hm/hafner/analysis/parser/MavenConsoleParser.java

according to whatever I have understood. 

And when I tried to push it to the GitHub page but there was an error saying push failed.