chaucoder / checker-plugin

Automatically exported from code.google.com/p/checker-plugin
0 stars 0 forks source link

toggling checker nature gives errors #5

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Choosing the 'toggle checker nature on project' menu item from the context menu 
at best has no effect and at worst gives odd error messages such as

error: Annotation processor 
'C:\cygwin\home\dcok\eclipseProjects\SMT\src\org\smtlib\SExpr.java' not found
1 error

I also get a popup containing

Checker processor 
'C:\cygwin\home\dcok\eclipseProjects\SMT\src\org\smtlib\SExpr.java' could not 
be found. Try adding checkers.jar to your project build path.

In this case, checkers.jar is explicitly in the project build path.  The source 
file given in the error message is a typical source file, not an annotation 
processor, and no where is it stated that it is an annotation processor.

I expected toggling the checker nature to enable auto checking when a build 
happens, but I may well have misunderstood its purpose.  In which case, a bit 
of documentation would be helpful.

A menu item that just toggles can leave the user confused as to what the actual 
state is (especially if an error message has happened).  A menu item with a 
check mark to indicate the state, or explicit separate enable/disable menu 
items would be better.

Original issue reported on code.google.com by c...@frontiernet.net on 21 Aug 2010 at 2:50

GoogleCodeExporter commented 8 years ago
You're right about the purpose of the action. I've enabled the behavior you 
expect for the menu item (a check mark appears when the nature is enabled). Can 
you give more information about when you get this error? Do you have any 
checkers enabled in the preferences?

Original comment by asumu.ta...@gmail.com on 25 Aug 2010 at 6:25

GoogleCodeExporter commented 8 years ago
Another note about the menu behavior: in the latest version on the update site 
(1.0.0) there are two actions: one to enable the nature and one to disable 
automatic checking. The reason it's been changed is because the new menu API 
doesn't easily support per-project menu/command states.

Original comment by asumu.ta...@gmail.com on 27 Aug 2010 at 9:51

GoogleCodeExporter commented 8 years ago
The error on toggling is gone (along with the toggle menu item).
The enable and disable auto checking work fine for me in 1.0.2 (Windows 7).
I consider it fixed.

Original comment by c...@frontiernet.net on 31 Aug 2010 at 12:33

GoogleCodeExporter commented 8 years ago
Closing the bug.

Original comment by asumu.ta...@gmail.com on 31 Aug 2010 at 6:05