Implement new features to a Jenkins Plugin - repost 2

Tasks ===== - To allow to display the source code for the function identified . This is something similar to the CPPtest plugin, showing the file absolute path, but for uvision, it is giving only a pure text file unless using a file reader to scan for the function name, but i am afraid there are multiple results found and that can be confusing - To display the file/function in jenkins plugin uvision - I would like to display the source code of the function that was seen in the coverage table. The source code is kept in the same workspace that is retrieved with the subversion each time during the build. I think a close match to this feature I have seen in the Jenkins static analysis plugin that is bind to the absolute path of the source code. - the file filter apply only for *.c file - i.e. in the coverage table, the file column represent the filename of the *.c file that the function is found, while the function name is something tricky, to locate a function instead of comments or other keywords. Any possible suggestion is welcome. - I don't think there is a standard pattern for the function otherwise we can use a regex string search - Perhaps it still be done using regex to search for the function name using "FName(" and there should not be any //, /*, /*...* before the FName, what do you think of this approach?