reproduce steps:
click "Rules" link
Search "xpath"
click the Java XPath rule that is not deprecated
click "create"
Fill in "name"/"key"/"Description"/"Message" as "should not use Collections.synchronizedMap" , change status as "ready" , set xpathQuery as //IDENTIFIER[#tokenValue='synchronizedMap']
click "create" button
click "edit" and notice "xpathQuery" field is empty which is unexpected.
fill the field "xpathQuery" with //IDENTIFIER[#tokenValue='synchronizedMap'] again
click "save" button
click "edit" and notice "xpathQuery" field is missing totally , which is unexpected.
run sonar runner again code that contains "Map test = Collections.synchronizedMap()"
no issue detected which is unexpected.
As test , Javascript XPath rule doesn't work either, and just test in Sonar 4.3.1 , both Java and Javascript XPath rule works.
java plugin version is 2.4
Anyone please give some suggestion or help reporting it to Sonar JIRA where I didn't have permission to report bug.
This is a known bug on SonarQube: SONAR-5575
Its fix is planned and should be available in a month or so. Feel free to vote and watch for the JIRA ticket.
Related
I created a custome rule using a template however I can not change the bug category. I select it and press Save but it isn't applied. Any ideas?
There is a similar question however we use sonarqube 6.7 and the tag solution doesn't work anymore.
Update: I found a workaround: When deleting the issue and selecting the type at creation time it seem to work. So it is probably a bug in sonar...
I'm looking for a way to change deprecated rules in SonarQube. I've got my own Quantity configuration, but Sonar shows that there are 2 deprecated rules, it suggest mi other ones, but I have no idea how to change/fix them. I've looked through internet and google, but there's no asnwer, can anyone help?
The suggested replacement rules should be linked. Click through. Now you're on the detail page of the suggested replacement. At the bottom next to "Quality Profiles", assuming you're logged in with the correct permissions, you'll see an "Activate" button. Use it to turn the replacement on in your profile. Now you can go back to the deprecated rule and remove it from your quality profile.
I am logged in as an administrator but I can't seem to find the menu to add new custom XPATH rules.
I'm following the steps from the link below :
http://docs.sonarqube.org/display/SONAR/Extending+Coding+Rules
"Once your new rule is written, you can add it SonarQube:
Login as an Quality profile administrator
Go to Quality Profile
Select one of the quality profiles for the language you wish to add the rule to
Look for the XPath rule template:"
I'm using sonarqube server 4.4.1
This is my Rules Tab:
Where is it located in that version?
The documentation is not up to date. Since SonarQube 4.4, custom rules are managed from the "Rules" space (directly accessible through the top navigation bar).
I am using 2.0 magneto connect. I am trying to update magneto 1.7 to 1.8. When i add "http://connect20.magentocommerce.com/community/Mage_All_Latest" and click install i am getting an error "Connection Error try again later." . I also removed the "http//" from the extension URL but its giving the same error. and when i click on "check for update" button. its does not show result. Just a blank page is displayed with title"Manage Existing Extensions" I was thinking that there may be some bug. I just on the development mode on and change the index file accordingly but there is no error. I did lot of R & D on this but did not get success.
Kindly check screenshot for better understanding
Yup, used the 2.0 extension straight from the “Get Extension Key” section. that will work
I found this thread about my problem.
Integrate TeamCity Reports to Confluence
I followed exactly the instructions, but I always get the same error.
My Widget looks like that:
And when im click on it, I get this error:
There are two things to check: first you'll need to check that the "external status widget" option is enabled for the build you're trying to show (this is in the General Settings section of the Build Configuration settings) and then verify you're using the proper URL (TeamCity 6.0 seems to use /externalStatus*.html*). You should be able to view the external status HTML page in a regular browser window so check that first, also there should be a little help icon beside the external status widget option in the build configuration settings, it provides a few more details on using the external status.