Oh, you're quite right about the guice code, I hadn't
spotted that (the Path column usually clips, have to get that 24" screen
;-).
Here's the full statistics on
warnings:
java warnings in guice code: 161
java warnings in non-guice code:
1
validation (html etc) warnings:
91
(I use WTP for the DWR project so that is the
producer of validation warnings.)
Maybe we could ask Tim to fix his
warnings?
I could clean up the "easy" validation warnings, but we
will not be able to get rid of all.
Best regards
Mike
On 5/31/07, Mike
Wilson <mikewse@...> wrote:
BTW: would it be possible to
adjust the checked-in Eclipse project settings to ignore suitable warnings
as not to fill up the Problems
View?
I think all the warnings are mostly in the Guice code. There are a
couple in the rest of the code, but they're prompting me to fix something...
So the options are:
- reduce the warning levels, which means I'll
be prompted less to comment my code, etc.
- fix the warnings in the
Guice code, which means editing Tim's code.
- mentally ignore them, which
is what I do - I generally don't use the problems view - I go on the markers
in the package view.
- configure the problems view to ignore them - I'm
sure it's possible.
I was working on 3, but happy to change strategy.
I'm not too keen on 1
though.
Joe.
