[Geotools-devel] coding conventions and eclipse warnings?

[Tara A. <tar...@gm...>]

I've just been tweaking my development environment, and I was curious 
about the many warnings that Eclipse generates. I have a working set for 
the app-schema module, and with the default settings, Eclipse generates 
over 9000 warnings. About
60% of these are connected to generics,
35 % to use of deprecated API,
4 % unnecessary code,
0.5% missing serialVersionUID,
0.2% dead code,
0.2% non-static access to static member,
leaving few assorted items of other types.

 If I turn off warnings in these categories, then I risk adding to the 
problem (if it is a problem). If I don't turn off the warnings, then 
this view becomes essentially useless because of so many occurrences. 
What, if any, are the geotools conventions about this? 

-- 
Tara Athan
Owner, Athan Ecological Reconciliation Services
tara_athan at alt2is.com
707-272-2115 (cell, preferred)
707-485-1198 (office)
249 W. Gobbi St. #A
Ukiah, CA 95482