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.
Some people report the following exception when running on JDK 1.4.x: java.lang.NoSuchMethodError: java.lang.Integer.valueOf(I)Ljava/lang/Integer; at org.netbeans.lib.gjast.ASScanner.intVal(ASScanner.java:289) at org.netbeans.lib.gjast.ASScanner.getValue(ASScanner.java:248) at org.netbeans.lib.gjast.ASScanner.nextToken(ASScanner.java:187) at com.sun.tools.javac.parser.Parser.skip(Parser.java:215) at com.sun.tools.javac.parser.Parser.syntaxError(Parser.java:224) at com.sun.tools.javac.parser.Parser.accept(Parser.java:257) at com.sun.tools.javac.parser.Parser.ident(Parser.java:509) at com.sun.tools.javac.parser.Parser.qualident(Parser.java:518) at com.sun.tools.javac.parser.Parser.annotation(Parser.java:2009) at com.sun.tools.javac.parser.Parser.modifiersOpt(Parser.java:1975) at com.sun.tools.javac.parser.Parser.modifiersOpt(Parser.java:1939) at com.sun.tools.javac.parser.Parser.typeDeclaration(Parser.java:2237) at com.sun.tools.javac.parser.Parser.compilationUnit(Parser.java:2181) at org.netbeans.lib.gjast.ASParser$ParseEngine.parse(ASParser.java:365) at org.netbeans.lib.gjast.ASParser$ParseEngine.compile(ASParser.java:303) at org.netbeans.lib.gjast.ASParser$ParseEngine.parse(ASParser.java:248) at org.netbeans.lib.gjast.ASParser.parse(ASParser.java:77) at org.netbeans.modules.javacore.parser.ASTProvider.createASTree(ASTProvider.java:83) at org.netbeans.modules.javacore.parser.ASTProvider.getASTree(ASTProvider.java:109) at org.netbeans.modules.javacore.parser.ASTProvider.getSourceText(ASTProvider.java:420) at org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.createMDRParser(ResourceImpl.java:478) at org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.checkUpToDate(ResourceImpl.java:555) at org.netbeans.modules.javacore.jmiimpl.javamodel.ResourceImpl.checkUpToDate(ResourceImpl.java:502) at org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.isValid(SemiPersistentElement.java:62) at org.netbeans.jmi.javamodel.JavaClass$Impl.isValid(Unknown Source) at org.netbeans.modules.javacore.ClassIndex.getClassByFqn(ClassIndex.java:462) at org.netbeans.modules.javacore.ClassIndex.getClassByFqn(ClassIndex.java:659) at org.netbeans.modules.javacore.jmiimpl.javamodel.JavaClassClassImpl.resolveClass(JavaClassClassImpl.java:120) at org.netbeans.modules.javacore.jmiimpl.javamodel.SemiPersistentElement.resolveType(SemiPersistentElement.java:659) at org.netbeans.modules.javacore.jmiimpl.javamodel.ParameterImpl.getType(ParameterImpl.java:91) at org.netbeans.jmi.javamodel.Parameter$Impl.getType(Unknown Source) at org.netbeans.modules.javacore.jmiimpl.javamodel.ParameterizedTypeImpl$TypedElementWrapper.getType(ParameterizedTypeImpl.java:632) at org.netbeans.modules.javacore.JMManager.traverseCallableFeature(JMManager.java:984) at org.netbeans.modules.javacore.JMManager.traverseClass(JMManager.java:1002) at org.netbeans.modules.javacore.JMManager.traverseClass(JMManager.java:993) at org.netbeans.modules.javacore.JMManager.traverseClass(JMManager.java:998) at org.netbeans.modules.javacore.JMManager.traverseClass(JMManager.java:991) at org.netbeans.modules.javacore.JMManager.traverseClass(JMManager.java:991) at org.netbeans.modules.javacore.JMManager.traverseClass(JMManager.java:991) at org.netbeans.modules.javacore.JMManager.traverseClass(JMManager.java:991) at org.netbeans.modules.javacore.JMManager.traverseResource(JMManager.java:972) at org.netbeans.modules.javacore.JMManager.resolveCPRoot(JMManager.java:954) at org.netbeans.modules.javacore.JMManager.resolveCodebases(JMManager.java:839) at org.netbeans.modules.javacore.JMManager$2.run(JMManager.java:793) at org.openide.util.Task.run(Task.java:136) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:330) at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:686)
This was fixed three weeks ago in the trunk: revision 1.83 of java/external/gjast.jar.scrambled.
I don't think so. I found a way how to reliably reproduce it in a build from the current CVS snapshot: 1) open a java file (or create a new class) 2) add the following field declaration: int a = 88888888888888888888888888888888888888888888888888; 3) wait 2 seconds - the exception is printed to the console Note I am using JDK 1.4.2.
Replaced 1.5 method with 1.4 version (it was staring right at me and I missed it!).
Verified in 4.2 (200507110943)
Reorganization of java component