Start here

Home
About Klocwork
What's new
Fixed issues
Release notes
Installation

Reference

C/C++ checkers
Java checkers
C# checkers
MISRA C 2004 checkers
MISRA C++ 2008 checkers
MISRA C 2012 checkers
MISRA C 2012 checkers with Amendment 1
Commands
Metrics
Troubleshooting
Reference

Product components

C/C++ Integration build analysis
Java Integration build analysis
Desktop analysis
Refactoring
Klocwork Static Code Analysis
Klocwork Code Review
Structure101
Tuning
Custom checkers

Coding environments

Visual Studio
Eclipse for C/C++
Eclipse for Java
IntelliJ IDEA
Other

Administration

Project configuration
Build configuration
Administration
Analysis performance
Server performance
Security/permissions
Licensing
Klocwork Static Code Analysis Web API
Klocwork Code Review Web API

Community

View help online
Visit RogueWave.com
Klocwork Support
Rogue Wave Videos

Legal

Legal information

Uninstalling checkers from the Server and build machines

To uninstall a custom checker from the Klocwork Server, you must remove it from the Klocwork Server and each build machine:

  1. Delete the checker zip file from the <projects_root>/plugins directory on the Klocwork Server.

    If the C/C++ checker is platform-specific, delete the zip file from <projects_root>/plugins/<platform-name>.

    If you are deleting a C# checker, delete the zip file from the <projects_root>/plugins/csharp directory.

  2. Wait 30 seconds to ensure the system updates the list of checkers.
  3. To uninstall the checker from the Server, run the kwdeploy sync command with the --url option, specifying the Klocwork Server host machine:
    kwdeploy sync [--url http(s)://<host>:<port>]
    

    The system removes the checker from the <server-install>/plugins directory.

  4. To uninstall the checker from each build machine, run the kwdeploy sync command with the --url option, specifying a build machine. Repeat this step for each build machine:
    kwdeploy sync [--url http(s)://<host>:<port>]
    
    Note: If you don't see a message that states that the directory was updated, run the command again.
  5. Run an integration-build analysis with kwbuildproject:
    kwbuildproject --tables-directory <dir> [<options>] <build_specification> 
    
  6. Have connected desktop users synchronize with the Klocwork Server by running a desktop analysis in their IDE or by using kwcheck.