Community
Participate
Working Groups
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 :)
"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.
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
