Community
Participate
Working Groups
Build ID: 8.0.2 (Indigo SR2) CQ:WIND00340413 In our product on top of Eclipse/CDT, we want to turn off CODAN by default since we have seen the extra error markers cause confusion for our users (especially since there are still some false positives), and we have seen performance problems with CODAN (bug 374746). We've been using plugin_customization.ini with this setting: org.eclipse.ui.workbench/PLUGINS_NOT_ACTIVATED_ON_STARTUP=...codan... in order to turn off the "plugins activated on startup" for CODAN. The problem with this approach is, that when our customers have an existing workspace in which they modified the "plugins activated on startup", our plugin_customization.ini does not apply and CODAN gets activated again. We need a reliable way turning off CODAN completely in our product, such that it cannot cause performance issues on startup or file access. Re-enabling it should be easy for those users who deliberately want it. Note that we do NOT want to disable each Codan Warning in turn (we'd rather keep the existing defaults for those), but we want a single reliable "master on/off" switch.
We would also like a reliable way to turn off Codan analysis programmatically. In PTP, we use primarily PTP Synchronized projects for HPC users. (Source code is synchronized between local and remote copies; include files are usually on the remote system; so Codan can't find many symbols ... among other things.) Codan does not work for synchronized projects so new users are confused, and end up turning Codan off. We would prefer to be able to programmatically turn Codan off (I would vote for an API not just a plugin_customization.ini setting) because it would be nice to be able to programmatically turn it back on. The Preferences page for Codan should also have a "turn it off" button as well, so that the user and turn it off without having to disable all the checkers. (Admittedly it's just a couple of clicks, but it's again confusing for new users)
We have the same issue. Codan doesn't work on remote projects so we need to be able to disable it on a per project basis with an API, so that we can leave it enabled for regular CDT project but disable them for our projects.
I agree again :) Codan is very useful, but can be confusing and disillusioning for new users, plus doesn't work in some cases (e.g. synch and remote projects). So can we turn it off, so that when they discover it later, it's love at first sight?
+1 for a "master on/off" switch accessible through both plugin_customization.ini and programmatically through preferences store.
