Stupid Question: Suppress Warnings vs Fixing What Ain't Broken

Question

Hey all,
I'm getting about 70 warnings in my code, mostly because I'm using anonymous classes to set up Actions as shown in the code snip below. This generates the warning "The serializable class does not declare a static final serialVersionUID field of type long" every time I create an Action this way:
final Action defaultUpAction = am.get(im.get(KeyStroke.getKeyStroke("control UP")));
          Action upAction = new AbstractAction(){  //warning generated here
               public void actionPerformed(ActionEvent e){
                    defaultUpAction.actionPerformed(e);
                    lastAction = "UP";
          };I understand what's causing the warning, and I even know how to fix it (or ignore the warning).
My question is, which is less of a hack? Do I just throw in a few SuppressWarnings annotations, or should I add a default serialVersionUID in each anonymous class? I'm not using the serialization functionality, but I might want to sometime in the future in which case suppressing the warnings would be a bad idea. Both solutions (adding a field I don't need or suppressing warnings instead of fixing them) seem a bit kludgey to me. Am I just being too touchy, or is there a better way?
Thanks

Answer 1

Thanks for the input, that does make quite a bit of sense. I suppose my hesitation comes from the feeling that although I was told by the higher-ups to "fix those warnings", all I'm doing is concealing them. I guess I shouldn't look at it that way, especially since I don't use serialization at all in any of my code (nobody else does, either). So in this case, simply suppressing the warnings probably makes more sense than adding fixes that won't be used anyway (and in fact may mislead future developers into thinking I'm using serialization somewhere).