remove compiler warnings

[GoogleCodeExporter]

I noticed that there are many compiler warnings now in the uimaFIT code base.  
I think this is due to project settings that were checked in by Richard.  
Regardless, they are sensible warnings that should be dealt with before a 1.0 
release.

Original issue reported on code.google.com by pvogren@gmail.com on 7 Jul 2010 at 11:25

[GoogleCodeExporter]

ok - I am considering this issue closed.  More specific issues may come up with 
compiler warnings which should be filed under a new issue.  We had a the 
compiler warning us about missing javadoc content and I addressed all of these 
in the main source directory.  However, I don't think it is reasonable to 
pollute our test code with a bunch of unnecessary comments.  Unless we commit 
to commenting all of our comments, then there will be a lot of warnings for 
javadocs that will mask other warnings.  

We are still getting compiler warnings for name shadowing and missing override 
annotation in the type system files.  I'm inclined to set these to ignore too.  

Original comment by pvogren@gmail.com on 16 Jul 2010 at 5:53

• Changed state: Fixed

[GoogleCodeExporter]

In the Eclipse project philosophy test and production code are often kept in 
two different projects. Unfortunately Eclipse does not support setting 
different warn levels for different parts of a project. So if the warnings are 
annoying, we'll have to turn them off.

Original comment by richard.eckart on 16 Jul 2010 at 8:39