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 ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
