Duplicates Finder (Java)

Project file type

To be able to run IntelliJ IDEA inspections on your code, TeamCity requires either an IntelliJ IDEA project file\directory, Maven pom.xml or Gradle build.gradle to be specified here.

Path to the project

Depending on the type of project selected in the Project file type, specify here:

• • For IntelliJ IDEA project: the path to the project file (.ipr) or the path to the project directory the root directory of the project containing the .idea folder).
  • For Maven project: the path to the pom.xml file. 

  • For Gradle project: the path to the .gradle file.

    This information is required by this build runner to understand the structure of the project.

    Icon

    The specified path should be relative to the checkout directory.

Detect global libraries and module-based JDK in the *.iml files

This option is available if you use an IntelliJ IDEA project. In IntelliJ IDEA, the module settings are stored in *.iml files, thus, if this option is checked, all the module files will be automatically scanned for references to the global libraries and module JDKs when saved. This helps ensure that all references will be properly resolved.

Check/Reparse Project

This option is available if you use an IntelliJ IDEA project. Click this button to reparse your IntelliJ IDEA project and import the build settings right from the project, for example the list of JDKs.

Working directory

Enter a path to a Build Working Directory if it differs from the Build Checkout Directory.<div class="aui-message error">
<p class="title">
<span class="aui-icon icon-error"> </span>
The license could not be verified: License Certificate has expired!
</p>
</div>Optional, specify if differs from the checkout directory.

<path_variable_name>

This field appears if the project file contains path macros, defined in the Path Variables dialog of IntelliJ IDEA's Settings dialog. In Set value to field, specify a path to the project resources to be used on different build agents.

JDK Home

Use this field to specify the JDK home for the project.

JDK Jar File Patterns

Click this link to open a text area where you can define templates for the jar files of the project JDK. Use Ant rules to define the jar file patterns.
The default value is used for Linux and Windows operating systems:

For Mac OS X, use the following lines:

IDEA Home

If your project uses the IDEA JDK, specify the location of the IDEA home directory

IDEA Jar Files Patterns

Click this link to open a text area, where you can define templates for the jar files of the IDEA JDK.

JDK

Select a JDK. This section details the available options. The default is JAVA_HOME environment variable or the agent's own Java.

JDK home path

The option is available when <Custom> is selected above. Use this field to specify the path to your custom JDK used to run the build. If the field is left blank, the path to JDK Home is read either from the JAVA_HOME environment variable on agent the computer, or from the env.JAVA_HOME property specified in the build agent configuration file (buildAgent.properties). If these values are not specified, TeamCity uses the Java home of the build agent process itself.

JVM command line parameters

You can specify such JVM command line parameters, e.g. maximum heap size or parameters enabling remote debugging. These values are passed by the JVM used to run your build.
Example:

Test sources

If this option is checked, the test sources will be included in the duplicates analysis.

Detalization level

Use these options to define which elements of the source code should be distinguished when searching for repetitive code fragments. Code fragments can be considered duplicated if they are structurally similar, but contain different variables, fields, methods, types or literals. Refer to the samples below:

Distinguish variables

If this option is checked, the similar contents with different variable names will be recognized as different. If this option is not checked, such contents will be recognized as duplicated:

Distinguish fields

If this option is checked, the similar contents with different field names will be recognized as different. If this option is not checked, such contents will be recognized as duplicated:

Distinguish methods

If this option is checked, the methods of similar structure will be recognized as different. If this option is not checked, such methods will be recognized as duplicated. In this case, they can be extracted and reused.
Initial version:

After analysiing code for duplicates without distinguishing methods, the duplicated fragments can be extracted:

Distinguish types

If this option is checked, the similar code fragments with different type names will be recognized as different. If this option is not checked, such code fragments will be recognized as duplicates.

Distinguish literals

If this option is checked, similar line of code with different litarels will be considered different If this option is not checked, such lines will be recognized as duplicates.

Ignore duplicates with complexity lower than

Complexity of the source code is defined by the amount of statements, expressions, declarations and method calls. Complexity of each of them is defined by its cost. Summarized costs of all these elements of the source code fragment yields the total complexity.
Use this field to specify the lowest level of complexity of the source code to be taken into consideration when detecting duplicates. For meaningful results start with value 10.

Ignore duplicate subexpressions with complexity lower than

Use this field to specify the lowest level of complexity of subexpressions to be taken into consideration when detecting duplicates.

Check if Subexpression Can be Extracted

If this option is checked, the duplicated subexpressions can be extracted.