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.
As a subtask of issue 17773 there is a need to document what API can be considered offical and what one needs to take care when creating such API. A set of recommendations and steps to take to follow when one wants to create an API should be the result of this efford.
Set target milestone to TBD
I do not think there will be any progress on this. Or am I wrong?
Sorry, I didn't realize that this issue was assigned to me. The goal of issue 17773 and others is to provide a mechanism for modules to have public APIs, that is, APIs with a committment to backward compatibility. I thought the intent was to use naming conventions to indicate a module's public APIs. This has been agreed upon, right? So what else remains in this task? It appears to be asking for something much larger, like a general discussion of good API design. If there are issues specific to the NetBeans APIs, that would be useful, but a request for general API guidelines is better served by books such as Effective Java. Yes, I believe the NB APIs would benefit if they had more closely followed the advice in Effective Java (Jarda, no need to "kill your idol"). So, lets discuss what needs to be done here.