-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Technical debt not showing anything with version 1.0 #21
Comments
Could you tell us which version of SQ you are using? |
Nice to hear from you. I am using SQ 6.7.2 and then I upgraded to 6.7.3, both are not working. |
Could you provide me with some numbers, what you are seeing and what you are expecting? |
Previously on version 0.1 the technical debt on average with one project can be from 30 mins to a few days. I think with version 0.1 there is alot of duplicated analysis of the same issue. With version 1.0 there is code smells but the technical debt is always 0. |
For example with using version 1, we have 1 project with 75 code smells, minor ones such as comments needed and disabled code. However the technical debt is showing 0. |
and btw I am using maven to do the code analysis. one package becomes one project in SQ |
Hi |
thanks alot :) |
Hi Please take a look at branch dev03_refactor. It should address this issue. We will create a release in the upcoming weeks. |
Thanks :) I will check and give that a try |
I tried compiling the branch dev03_refactor, however it has some errors/conflicts like these in some files (4 of them, 1 test). package be.i8c.codequality.sonar.plugins.sag.webmethods.flow.metric; <<<<<<< HEAD import com.sonar.sslr.api.AstNode; import be.i8c.codequality.sonar.plugins.sag.webmethods.flow.visitor.NodeMetricsVisitor; public class NodeFileMetrics { private final NodeMetricsVisitor fileLinesVisitor = new NodeMetricsVisitor(); /**
package be.i8c.codequality.sonar.plugins.sag.webmethods.flow.visitor <<<<<<< HEAD
|
After trying to modify the code myself to get it to compile and build am also getting these errors in parsing. [ERROR] Unable to parse file: xx/xx/xx/node.ndf --> Valuesversion2.0 |
@benedictbasa |
Should be fine now, i just created my own quality profile. |
I have used version 0.1 a few months ago and when I switched to version 1.0 today, the technical debt in terms of effort is not showing properly. Any thoughts?
The text was updated successfully, but these errors were encountered: