Bug 535173 - Remove serialization warnings
Summary: Remove serialization warnings
Status: CLOSED DUPLICATE of bug 479928
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2018-05-27 18:25 EDT by Alberto Alonso CLA
Modified: 2018-05-28 11:37 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alberto Alonso CLA 2018-05-27 18:25:35 EDT
Reading http://openjdk.java.net/jeps/154

suggest classes lacks of serialization ID seems confusing and misleading

It is a nice idea, broken in several ways:

- IDE do not warn if other classes use same ID as others (copy/paste do exists, sadly)
- IDE do not warn if you modify a class so ID is invalid
Comment 1 Dani Megert CLA 2018-05-28 06:13:05 EDT
What exactly are you requesting us to do?
Comment 2 Alberto Alonso CLA 2018-05-28 09:35:28 EDT
This come after a twitter discussion

https://twitter.com/albfanjul/status/1000865733595844608?s=19

I think remove that validation is a good idea

But is ok for me not accept this issue, just want to move discussion to a more formal workflow
Comment 3 Dani Megert CLA 2018-05-28 10:11:23 EDT
(In reply to Alberto Alonso from comment #2)
> This come after a twitter discussion
> 
> https://twitter.com/albfanjul/status/1000865733595844608?s=19
> 
> I think remove that validation is a good idea
> 
> But is ok for me not accept this issue, just want to move discussion to a
> more formal workflow

I read that. What exactly are you proposing in detail?
Comment 4 Alberto Alonso CLA 2018-05-28 11:31:49 EDT
- Set warning for "Serializable class without serialVersionUID" default to false
Comment 5 Dani Megert CLA 2018-05-28 11:37:24 EDT
That does not make sense given http://openjdk.java.net/jeps/154 got withdrawn.

*** This bug has been marked as a duplicate of bug 479928 ***