Closed kaszuster closed 10 years ago
The Java bytecode does not provide line number information about declarations of classes, fields or methods - thus the information cannot be provided to the report/sonar. Could be solved by switching the scanners to work on source code.
Currently the issues created by jQA link to a resource that violate a certain constraint e.g. a java class file. After opening the issue in SonarQube you can observe that all the information are correct, the only downside is, that you cant see any code.
I would like to see, that the issue is not only linked to the class's resource but also to the line of code where the class is defined to see the actual source code.
The same applies to methods. A constraint that returns a certain method should not only be linked to the method's class resource but also to the line of code where the method was defined.