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

Bug 336398

Summary:	Divide launch options for internal checkers and external checkers
Product:	[Tools] CDT	Reporter:	Alex Ruiz <alruiz>
Component:	cdt-codan	Assignee:	Elena Laskavaia <elaskavaia.cdt>
Status:	RESOLVED FIXED	QA Contact:	Elena Laskavaia <elaskavaia.cdt>
Severity:	normal
Priority:	P3	CC:	alruiz, cdtdoug, eclipse.sprigogin
Version:	8.0
Target Milestone:	8.0
Hardware:	PC
OS:	Linux
Whiteboard:

Description Alex Ruiz

2011-02-04 16:26:34 EST

Build Identifier: I20101208-1300

Currently, there is a single launch configuration (with build or on in editor) for codan checkers per project. I would think this would be fine for internal checkers. External checkers on the other hand might have different performance or behavior and it would be useful that each external checker has its own launch configuration.

For example, we could have all internal checkers to run in the editor while some external checker that calls an external command-line tool to be executed with build only.

In short, we can keep a single launch configuration for all internal checkers. But, for external checkers, it would be handy to have a launch configuration *per* checker.

Thanks,
-Alex

Reproducible: Always

Steps to Reproduce:
Not steps to reproduce. This bug is more a discussion than a bug :)

Comment 1 Elena Laskavaia

2011-02-07 21:07:47 EST

"Launch configuration" is eclipse specific term that is used for launching programs. You are not talking about these launch configurations right? I was planning to have this "launch mode" per checker, but it is getting pretty complex. Right now there is no concept of external checker btw.

Comment 2 Elena Laskavaia

2011-02-23 21:26:11 EST

Lets say fixed. I added a Launch tab for each checker - it can override default user settings. There is still no concept of external checker though and checker can turn off like as you type itself if does not mean to be run this way