https://issues.apache.org/bugzilla/show_bug.cgi?id=56682
--- Comment #11 from Ashish Sureka <[email protected]> --- Sebb: I was referring to line numbers for the source code. Ashish: Mentioning line-number of the source code and inserting line-numbers in the report – both are useful. I will work towards adding source-code line numbers also (good feature). Sebb: There are likely other anti-patterns that are common in Unit test code. It would probably be better to produce separate reports for the two source trees. Ashish: I agree. This will be a good feature. However, I need to come-up with a solution to differentiate between test-code and non-test-code. Sebb: Note that there are already a lot of other such tools. For example, Findbugs. Ashish: The focus of my tool is Exception handling anti-patterns and code-smells. While there are several anti-pattern detecting tools, they do not cover exception handling anti-patterns. Here’s the link to FindBugs Bug Descriptions and it does not cover the anti-patterns in my tool (+ I am implementing more anti-patterns which are not covered in FindBugs). Thanks again for the inputs. FYI – I am submitting issue-reports to some more open-source Java projects and I a observing that some anti-patterns from the report are accepted as issues and assigned for fix. -- You are receiving this mail because: You are the assignee for the bug.
