Excellent point. IDEs should serve the need of developers, not the other
way around. I have to admit that most Eclipse warnings are quite useful.
Apart from the serialID thing, another warning/error message I probably
want to get rid of is related to ant custom tasks. Whenever Eclipse
cannot find the class implementing the custom ant task, there is an
error message entry in the "problem" window.
Cheers,
Cedric
Philip Johnson wrote:
Hi!
Actually, there is no real need to provide serialId fields in
hackystat,so the default id should be fine. To get rid of the
stupid eclipse
warning, one could just disable it
(Preferences/java/Compiler/Error&Warnings/PotentialProblems/Serializable)...
Cheers,
Christoph
Christoph makes a really excellent point. Why add several hundred lines of code to the
system to define a construct that isn't actually of any use in our situation, merely
because Eclipse happens to raise a "potential problem" warning? That's
totally counterproductive: it makes the code harder to understand.
Imagine if you will in 10 years, when someone asks us why there's all of these unecessary serialVersionUid declarations, what are we going to say? "Well, back in the mid-2000's, we were using this editor called Eclipse, and it turns out that Eclipse would raise a superfluous warning, so to get rid of the warning messages we added 500 LOC to the system." To which the person will respond, "So, couldn't you have simply disabled the warning?"
So. One thing I'd like to figure out is what warnings in Eclipse we _should_ enable? Any nominations?
Cheers,
Philip
