Versions Compared

Old Version 1

changes.mady.by.user Anna Stuchlik

Saved on

compared with

New Version Current

changes.mady.by.user Anna Stuchlik

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The rulemap.xml file that contains information about rule mapping. The file is created when you modify rule properties with the rule map editor (see Customizing Static Analysis Rules), or can be exported from the DTP Rule Map Editor (see the DTP documentation for details).
  • custom rules created with Parasoft RuleWizard
Warning
iconfalse

If the rulemap.xml is The rule mapping available in this directory , the rule mapping will affect all built-in and user test configurations that are locally available.

...

  1. Click  Parasoft in the menu bar and choose 

    Conditional Contentproduct: (jtest)product: (jtest)sv-attr:0A01020401598D973E6641760F8AF4E50A01020401598D973E671AAA268425A3

    Preferences (Eclipse), Options (NetBeans) or Settings (IntelliJ).

  2. Select Configurations.
  3. Enable the User rule map option and provide the path to the directory. The default path is [INSTALL_DIR]\rules\user.
Info
titleBackward Compatibility

From version 10.4, the local user rule mapping is only applied to local test configurations (see Viewing Rule Mapping). If DTP-shared rule mapping is configured, it only affects test configurations stored in DTP.

In versions earlier than 10.4:

  • any configured rule mapping (local or DTP-shared) applied to both local and DTP configurations,
  • if rule customizations were simultaneously available locally and on DTP, the rule mapping information was merged,
  • if a particular rule was customized both locally and on DTP, the local mapping had priority over the DTP customization.

To ensure backward compatibility for versions earlier than 10.4,  add the rules.mappings=all setting to the list of advanced settings in your IDE, or to the .properties configuration file; see Customizing Advanced Settings.