SonarQube Plugins

Capability to make difference between message and name of a rule

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: FLEX-0.4
  • Fix Version/s: FLEX-1.0
  • Component/s: Flex
  • Labels:
    None
  • Number of attachments :
    0

Description

in
http://svn.codehaus.org/sonar-plugins/trunk/flex/src/main/resources/org/sonar/plugins/flex/flexpmd/rules.xml
no difference is made between message and name.
If we add that parameter, no field can be used to store both the name and message since only one can be stored in the sonar org.sonar.api.rules.Rule class (message is stored in name field and it does not makes any sense to have a rule named "This private attribute (

{0}

) does not seem to be used "

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. SONARPLUGINS-745 Confusing Flex PMD rules name

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Freddy Mallet added a comment -

Manually tested

Show
Freddy Mallet added a comment - Manually tested
Hide
Permalink
Fabrice Bellingard added a comment -

Messages are now correctly displayed, but they rely on a static properties file that is embedded in the plugin (because the rule repository definition of Sonar does not contain a field for messages).

Show
Fabrice Bellingard added a comment - Messages are now correctly displayed, but they rely on a static properties file that is embedded in the plugin (because the rule repository definition of Sonar does not contain a field for messages).

People

  • Assignee:
    Fabrice Bellingard
    Reporter:
    Jean-Hervé Laveau
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: