Bugzilla – Full Text Bug Listing
| Summary: | Unused private method warning doesn't know about read/writeObject | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Wilhelm Fitzpatricck <rafial> |
| Component: | Core | Assignee: | Philipe Mulet <philippe_mulet> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 2.1 | ||
| Target Milestone: | 2.1 RC1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Somehow the description got mangled. Repeating:
If you turn on the new compiler warning that detects unused private fields and
methods, and you have Serializable classes that use the magic methods
private void writeObject(java.io.ObjectOutputStream out)
or
private void readObject(java.io.ObjectInputStream in)
A warning will be generated that these methods are not used. The warning code
should recognize such "magic" methods (as I recall there are a few other special
private methods as part of serialization) and not issue the warning.
This behavior is observed with the I20030213 integration build.
Support got added in latest (not yet integrated). |
If you turn on the new compiler warning that detects unused private fields and methods, and you have Serializable classes that use the magic methods private void writeObject(java.io.ObjectOutputStream out)