SonarQube Plugins

taglist violations configable / NLOC

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: TAGLIST-0.6
  • Fix Version/s: None
  • Component/s: TagList
  • Labels:
    None
  • Environment:
    sonar
  • Number of attachments :
    0

Description

Current taglist plugin just shows alerts based on number of taglist violations it does not matter if it is a big or small project it would be nicer if the taglist alerts can be adjusted based on NLOC

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Evgeny Mandrikov added a comment -

Taglist plugin itself never creates alerts. So could you please clarify what do you mean?

Show
Evgeny Mandrikov added a comment - Taglist plugin itself never creates alerts. So could you please clarify what do you mean?
Hide
Permalink
Myster Mask added a comment -

I guess this is somewhat related to Point 4 of this comment:
http://jira.codehaus.org/browse/SONARPLUGINS-1105?focusedCommentId=270778&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270778
(from SONARPLUGINS-1105)

Having just raw numbers of TODOs/FIXMEs/NOSONAR/NOPMD is nice but it is not so useful as a metric since you likely find more NOPMDs in projects with a large amount of sources. This makes it difficult to define meaningful limits because you can only specify a total without taking into account how much code is really affected (e. g. having 10 NOPMDs might look suspecious in a small project but not so much in a big one => a limit like "1 NOPMD / 1000 lines of code" makes more sense).

Show
Myster Mask added a comment - I guess this is somewhat related to Point 4 of this comment: http://jira.codehaus.org/browse/SONARPLUGINS-1105?focusedCommentId=270778&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-270778 (from SONARPLUGINS-1105 ) Having just raw numbers of TODOs/FIXMEs/NOSONAR/NOPMD is nice but it is not so useful as a metric since you likely find more NOPMDs in projects with a large amount of sources. This makes it difficult to define meaningful limits because you can only specify a total without taking into account how much code is really affected (e. g. having 10 NOPMDs might look suspecious in a small project but not so much in a big one => a limit like "1 NOPMD / 1000 lines of code" makes more sense).

People

  • Assignee:
    Unassigned
    Reporter:
    Joel Tomasoa
Vote (0)
Watch (0)

Dates

  • Created:
    Updated: