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.
Everyday I find following mail in my mailbox and I do not want it there especially because nothing wrong in going on. Jesse, you did the change, Rudolf, you run the sigtest. Please talk to each other and stop sending false notifications. Thank you. yarda API signature test results -------------------------- Note: This file lists INCOMPATIBLE API changes made since the 'netbeans332' release APIChangeTest Report Base version: 1.3.1_02 Tested version: 1.3.1_03 Missing Superclasses or Superinterfaces --------------------------------------- org.openide.loaders.ExtensionListEditor:superclass org.netbeans.beaninfo.editors.ExtensionListEditor
OK, I am happy to help, but I do not know where the sources and scripts for sigtest are....
Hey, wake up, the emails are generated everyday and I am tired of deleting them.
Still broken.
Fixed by falsing openide's signature file for NetBeans 3.3.2. On class org.openide.loaders.ExtensionListEditor changed reference to superclass from org.netbeans.beaninfo.editors.ExtensionListEditor to java.lang.Object (as it's now in trunk). Yarda has assured me, that this change of signature file is safe. Backup file openide_nb332_nackup-non-falsed.sig left in place for potential rollback.
I'd like to verify, and I can say that no false alarm today has been sent. I believe that the change of parent class is compatible, but let Jesse verify it, he did the change.
Change of parent class should be compatible in this case, in the sense that the superclass was not part of the APIs and it is therefore forbidden to have used any superclass methods. Anyway I hope so. The original condition of extending a non-public class was a physical API defect anyway, so for such cases it is of questionable value to try to save compatibility - in 3.4, resolving the superclass from a module classloader would fail anyway.
Ok.