Hi Steve, If you have a chance, I would suggest go ahead and update the eclipse ide prefs. On the top of my head, I think at a min we should fix the Deprecation warnings, Java Generic Types Warnings, Unused classes/imports/variables, Checkstyle?- just in case we decide on a standard code styling format...
--Pei > -----Original Message----- > From: Steven Bethard [mailto:[email protected]] > Sent: Wednesday, October 24, 2012 12:43 PM > To: [email protected] > Subject: warnings policy? > > I think it would be nice if cTAKES aimed for zero warnings. Right now, I see > 3388 warnings, though this number is probably different for you depending > on your settings. > > One step we could take in this direction is making sure that we all see the > same warnings. For Eclipse, this would mean making sure that all cTAKES > projects have exactly the same .settings/org.eclipse.jdt.core.prefs. For an > example of one possible set of warnings we could choose, see ctakes- > temporal/.settings/org.eclipse.jdt.core.prefs. > > I don't feel strongly about exactly which warnings are on or off, but I would > love to see us be consistent across the different cTAKES projects. > > Steve > > P.S. On the Maven side, it looks like we're already using -Xlint with the > maven-compiler-plugin, so that's good. But I suspect most people are like me > and they won't fix a warning unless there's an annoying little yellow sign in > Eclipse. ;-)
