This is a known issue, and will be fixed in the next release, by providing a flag as to whether == between enums should receive a warning. Since there are differences between .equals() and == for enums (tricky classloader issues, mostly), I will be making the check optional.
This is a known issue, and will be fixed in the next release, by providing a flag as to whether == between enums should receive a warning. Since there are differences between .equals() and == for enums (tricky classloader issues, mostly), I will be making the check optional.
--Dave Griffith