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.
RE: [mdr-cvs] CVS update: MODIFIED: xmidiffs ... > October 2nd, 2002 > ... bugfix in bytecode generators... I think there is a regression in this checkin. This module was working fine yesterday. After I did a "cvs update" and "ant clean" in mdr and then rebuilt from nbbuild, I consistently get: Compiler.run(CompilationEngineImpl.java:290) java.lang.VerifyError: (class: org/brianlsmith/smn/directory/DirectoryEntryClass $Impl, method: _createInstance signature: ([Ljava/lang/Object;)Ljavax/jmi/reflec t/RefObject;) Inconsistent stack height 3 != 4 at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:1590) at java.lang.Class.getConstructor0(Class.java:1762) at java.lang.Class.getConstructor(Class.java:1002) at org.netbeans.mdr.handlers.BaseObjectHandler.getHandler(BaseObjectHand ler.java:208) at org.netbeans.mdr.handlers.BaseObjectHandler.getHandler(BaseObjectHand ler.java:166) at org.netbeans.mdr.handlers.PackageProxyHandler._handleGetClassProxy(Pa ckageProxyHandler.java:102) at org.brianlsmith.smn.directory.DirectoryPackage$Impl.getDirectoryEntry (Unknown Source) at org.brianlsmith.smn.directory.DirectoryManager.createEntry(DirectoryM anager.java:79) at org.brianlsmith.smn.netbeans.compilers.TransientSmnCompiler.executeIn Transaction(TransientSmnCompiler.java:38) at org.brianlsmith.smn.netbeans.compilers.SmnCompiler.execute(SmnCompile r.java:31) at org.brianlsmith.smn.netbeans.compilers.SmnCompilerGroup.start(SmnComp ilerGroup.java:28) at org.netbeans.core.compiler.CompilationEngineImpl$CompilerThread$Group Compiler.run(CompilationEngineImpl.java:290)
Created attachment 7575 [details] metamodel
I confirm that deleting MDR module and then doing a "cvs -q checkout -D yesterday -P mdr" at 20:30 PDT and then rebuilding causes this problem to go away. So, it is indeed a regression.
should be fixed
My module is happy again today. Marking this issue "verified fixed".