Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 336770

Summary: Specify a way to simply enable/disable external checkers.
Product: [Tools] CDT Reporter: Alex Ruiz <alruiz>
Component: cdt-codanAssignee: Project Inbox <cdt-core-inbox>
Status: RESOLVED WONTFIX QA Contact: Elena Laskavaia <elaskavaia.cdt>
Severity: normal    
Priority: P3 CC: alruiz, cdtdoug, eclipse.sprigogin
Version: 8.0   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description Alex Ruiz CLA 2011-02-09 17:32:54 EST
Build Identifier: I20101208-1300

This is related to Bug 336398 ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=336398 .)

Currently the "Code Analysis" property page (per project) lists all the problems that the current internal checkers can detect. Users can enable individual ones and select their priority. In the case of an external checker, we really don't have control of the all the problems the external tool can detect (at least not in my case.) We simply need to enable/disable an external checker. We might also have checker-specific configuration, that at the end, will be translated to different flags passed to the external tool. 

In short, codan needs a "project properties" UI where users can enable/disable an external checker (and optionally configure checkers individually)

Reproducible: Always

Steps to Reproduce:
1. Create a new C++ project.
2. Right-click the top-folder of the project and select the menu "Properties" from the pop-up menu.
3. In the "Project Properties" dialog, navigate to "C/C++ General" -> "Code Analysis" in the tree-view on the left-hand side of the dialog
4. Take a look at the preferences, they allow users enable/disable individual problems and set their severity, something that is not always possible to do in external checkers.
Comment 1 Elena Laskavaia CLA 2011-02-09 23:18:34 EST
I don't understand a need for it.
If you cannot pass specific problems enablement to your "external tool"
just create a one problem - i.e. "Lint problem"
If you can - then they have to enabled by user differently.
Codan will handle it now - checker will run if at least one problem enabled 
which it can produce.