I think this is also likely to cause the
Java compiler to spit out a warning. However, if you look at the suggested fixes that Eclipse offers, you'll see that there's also an option to ignore the missing Serial version ID. It causes an annotation to be placed just ahead of the class definitions.
Actually, it's not a bad idea to use the serial version ID. It doesn't require much space and it may someday keep you out of trouble when working with serialized objects that are being passed around between different releases of code.
Then again, there are times when you get this because you're working with a class that's defined as serializable even though you never intend to actually serialize it. Which is why you have the option to suppress the warning.
The secret of how to be miserable is to constantly expect things are going to happen the way that they are "supposed" to happen.
You can have faith, which carries the understanding that you may be disappointed. Then there's being a willfully-blind idiot, which virtually guarantees it.