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

Managing project branches

This article shows you how to:

  • set up and analyze a Klocwork project for branched code
  • run kwxsync to synchronize issue status changes and comments across projects, so that developers need to investigate and cite detected issues only once for source code that is shared by multiple projects
  • run kwmatch to match issues across projects, so that Klocwork Static Code Analysis displays a list of other projects in which a particular issue appears

While kwxsync and kwmatch both help you to manage branched projects, they serve different purposes, and it is not necessary to run both tools. Cross-project issue synchronization with kwxsync saves time in citing issues that occur in multiple projects. Cross-project issue matching with kwmatch can help you prioritize when citing issues -- an issue that appears in multiple projects likely has a high priority.