This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Deprecate use of Node.setName, etc. for future | ||
---|---|---|---|
Product: | platform | Reporter: | Jesse Glick <jglick> |
Component: | Nodes | Assignee: | Jaroslav Tulach <jtulach> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | CC: | jtulach, pzavadsky, ttran |
Priority: | P3 | Keywords: | API |
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://openide.netbeans.org/servlets/ReadMsg?msgId=238545&listName=dev | ||
Issue Type: | TASK | Exception Reporter: | |
Bug Depends on: | |||
Bug Blocks: | 19446, 19504, 32744 |
Description
Jesse Glick
2002-04-12 17:45:12 UTC
Some relevant bugs caused by, or whose solution was made more complex by, the mixing of set-style vs. override-style idioms, are listed in the "blocks" area here. I will add more if I remember any. Also cf. DataNode.java 1.52 which seems to be similar. I see that AbstractNode.setPreferredAction was introduced in 3.5 along with a nonfinal getPreferredAction. This is unfortunate (see issue #32744 for some problems it contributes to). Is it too late to delete the setter method before 3.5 is released? Taking over the node bugs from phrebejk. Reassigning to new module owner Tomas Holy. Too late. According to our compatibility policy I would need to go through all our sources and clean them up. I am not going to do that. |