Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3
Wiki Markup
{iframe:src=http://update.sonarsource.org/plugins/uselesscodetracker.html|width=700|height=250|frameborder=0}
Your browser does not support iframes.
{iframe}

Description / Features

The objective of this plugin is to report on the number of lines that can be reduced in an application. It currently works on 3 axes:

1. Report the number of duplicated lines that could be reduced
Currently SonarQube tells you that you have 50 lines involved in a duplication. But it does not easily tell you whether this is two blocks of 25 lines (in which case you can save 25 lines) or 5 blocks of 10 lines (in which case you can save 40 lines). With this plugin you get this extra information. The algorithm is as follows: assuming that refactoring will not cross boundaries of sub-projects (no support for cross-project duplication detection), first occurrence of a duplicated block will survive and all others can be removed.

2. Report on the number of lines of dead code that could be reduced (only for Java)
Currently SonarQube reports on the number of unsused private method within your application. This can be done through the PMD:UnusedPrivateMethod rule or through the  SQUID:UnusedPrivateMethod rule. This plugin calculates the number of lines that can be saved for each of them and aggregates them.

3. Report on the number of lines of potential dead code that could be reduced (only for Java)
Currently SonarQube reports on the number of unsused protected methods within your application. This can be done through the SQUID:UnusedProtectedMethod rule. This plugin calculates the number of lines that can be saved for each of them and aggregates them.

Note that an unused protected method could be used outside the application through inheritance. This is why we call it potential dead code.

Include Page
Include - Plugin Installation
Include - Plugin Installation

Usage

  1. Switch on the coding rules that you want to monitor in your quality profile
  2. Run a quality analysis

Change Log

JIRA Issues
anonymoustrue
titleVersion 0.6
height100
renderModestatic
width900
columnstype;key;summary;priority
urlhttp://jira.codehaus.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?fixfor=19348&pid=11911&sorter/field=issuekey&sorter/order=DESC&tempMax=1000

 

JIRA Issues
anonymoustrue
titleVersion 0.5
height100
renderModestatic
width900
columnstype;key;summary;priority
urlhttp://jira.codehaus.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?fixfor=18274&pid=11911&sorter/field=issuekey&sorter/order=DESC&tempMax=1000

 

JIRA Issues
anonymoustrue
titleVersion 0.4
height50
renderModestatic
width900
columnstype;key;summary;priority
urlhttp://jira.codehaus.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?fixfor=17508&pid=11911&sorter/field=issuekey&sorter/order=DESC&tempMax=1000

 

JIRA Issues
anonymoustrue
titleVersion 0.2
height50
renderModestatic
width900
columnstype;key;summary;priority
urlhttp://jira.codehaus.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?fixfor=16904&pid=11911&sorter/field=issuekey&sorter/order=DESC&tempMax=1000