groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From paulk-asert <...@git.apache.org>
Subject [GitHub] groovy pull request #:
Date Tue, 03 Apr 2018 02:54:35 GMT
Github user paulk-asert commented on the pull request:

    https://github.com/apache/groovy/commit/1bcaaeaf60078dd5a9aca5cbf1df8f45de68db60#commitcomment-28387216
  
    To keep serializability compatible within 2.4 we can add serialVersionUID values generated
from the 2.4 codebase. We can then move those forward onto the other branches. If there has
been no changes to any fields, modifiers, inherited fields etc, then this won't be required
but then it shouldn't be showing up in the discrepancy report. So it's only the cases in the
report where something has changed - often we added a final modifier to a non-changing field.
You can't generate the serialVersionUID from the modified class in that case. But as I said,
there seems to be some cases which are generating false positives. I think where nested classes
are involved.


---

Mime
View raw message