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.
According to http://www.netbeans.org/servlets/ReadMsg?msgId=614306&listName=api-changes there has been unexpected change in an API of some web module. As we want to ensure the best quality of all the API we provide, we have to prevent random changes and rather follow the review processhttp://openide.netbeans.org/tutorial/review-steps.html in order to ensure that the API fits into overall NetBeans architecture, is meaningful, well documented and tested in order to be useful in long term. I have created this P1 issue to remind the team that without proper review it is not possible to release such API and it should not even appear in production build. I hope that this will help the team to correct the situation.
Good point, Jarda. I suggest we take this API to the architecture review. Reassigning to Milan.
I am taking this into account. Yes it is intended to be an API. However, we haven't declared this API as public yet (in manifest file). The issue is that the package name starts with org.netbeans.api. I am working on the first implementation now. I'll start working on architecture document this week.
According to stability categories in http://openide.netbeans.org/tutorial/api-design.html#life everything in org.nb.api is supposed to have official stability if released. However if you declare Public-Packages: - in the manifest, this rule might not apply. Can you point me to the manifest file, so I can verify that the Public-Packages are really restricted? In such case we might downgrade this to P2, IMHO.
Public packages haven't been specified in web/core/manifest.mf file yet.
For compatibility reasons, not specifying PublicPackages, means that everything is public. You have to implicitly add Public-Packages: -
DD API passed through the regular Netbeans API process.
v