Paul --- give it a try! I'm not wedded to these settings, let's see if warnings work better (when extraneous warnings are turned off).
On 8/24/05, Paul Ferraro <[EMAIL PROTECTED]> wrote: > But by doing this we are *decreasing* the visibility of real compilation > errors since they are now indiscernable from non-critical warnings. > More importantly, when the Eclipse compiler flags these things as errors > it does not generate .class files (as if there was an actual compilation > error) and I can no longer run a one-off junit tests from within Eclipse > if a dependency file is flagged as an error. This is quite > couterproductive to the way I am used to using Eclipse. I guess this > wouldn't be an issue if the current cvs head branch didn't contain so > many of these non-critical errors. > I still don't understand why we can't just declassify the warnings we > don't care about (e.g. missing type parameters for generics) by setting > the compiler settings to "ignore", leave warnings we do care about as > "warnings", and reserve the "error" setting for actual compilation errors. > > Paul > > Richard Lewis-Shell wrote: > > > I prefer them to be errors. Warnings are too easy to ignore, even > > when there are only a few of them... > > > > Paul Ferraro wrote: > > > >> But they are not errors... I'd rather be able to easily identify > >> compilation errors than identify warnings. > >> e.g. I had to revert the compiler warning settings so that I could > >> track down the uncompilable AbstractFormComponent in CVS head. > >> If you are having an issue with too many warnings, then wouldn't it > >> be better to change the compiler settings to "ignore" the warnings > >> you want to ignore (e.g. warnings regarding generics), and revert > >> these settings back to "warning"? > >> > >> Howard Lewis Ship wrote: > >> > >>> Because those are errors? Normally, I'd want them to be warnings and > >>> we could get rid of those warnings, but with JDK 1.5 and all the > >>> deprecation going on, warnings are no longer useful ... lost in a sea > >>> of useless information about generics and such. > >>> > >>> On 8/23/05, Paul Ferraro <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>> Is there a reason why the org.eclipse.jdt.core.prefs file in CVS is > >>>> set > >>>> to flag certain "unused code" warnings (e.g. unused imports, > >>>> unreferenced local variables, etc.) as errors? > >>>> > >>>> Paul > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>> For additional commands, e-mail: [EMAIL PROTECTED] > >>>> > >>>> > >>>> > >>> > >>> > >>> > >>> > >>> > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
