Community
Participate
Working Groups
i tried to save my project and an error-message popped up that said: "Errors during build"... i clicked on "details" and it said:"java.lang.NullPointerException encountered while running org.eclipse.jdt.internal.core.builder.JavaBuilder".. this happened after i added a string variable-declaration..
Can you provide steps to reproduce ? Also, could you paste in this PR the content of the .log file (under your workspace .metadata/ folder).
i declared quite a lot of string variables but didnt use them yet. after that i tried to save. in "preferences -> java -> compiler" the field "unused parameters" was on "warning".. thats how the exception was produced. later i found out that if i turn this compiler-option to "ignore" the exception doesnt occur anymore... (probably there were too many warnings???) ----------------------------------- log-file: ----------------------------------- !MESSAGE Errors during build. !SUBENTRY 1 org.eclipse.jdt.core 2 75 Jun 25, 2002 11:06:51.328 !MESSAGE java.lang.NullPointerException encountered while running org.eclipse.jdt.internal.core.builder.JavaBuilder. !STACK 0 java.lang.NullPointerException at org.eclipse.jdt.internal.compiler.CompilationResult.computePriority (CompilationResult.java:99) at org.eclipse.jdt.internal.compiler.CompilationResult.quickPrioritize (CompilationResult.java:223) at org.eclipse.jdt.internal.compiler.CompilationResult.getProblems (CompilationResult.java:157) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.updateProblemsFor (AbstractImageBuilder.java:375) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.acceptResult (AbstractImageBuilder.java:98) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:349) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile (AbstractImageBuilder.java:218) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile (AbstractImageBuilder.java:165) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build (BatchImageBuilder.java:50) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll (JavaBuilder.java:174) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build (JavaBuilder.java:94) at org.eclipse.core.internal.events.BuildManager$2.run (BuildManager.java:383) at org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java:802) at org.eclipse.core.runtime.Platform.run(Platform.java:416) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:119) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:173) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:183) at org.eclipse.core.internal.events.BuildManager$1.run (BuildManager.java:143) at org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java:802) at org.eclipse.core.runtime.Platform.run(Platform.java:416) at org.eclipse.core.internal.events.BuildManager.basicBuild (BuildManager.java:157) at org.eclipse.core.internal.events.BuildManager.build (BuildManager.java:208) at org.eclipse.core.internal.resources.Workspace.build (Workspace.java:142) at org.eclipse.jdt.internal.ui.preferences.CompilerPreferencePage$4.run (CompilerPreferencePage.java:646) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run (ModalContext.java:98)
This was resolved in build 20020527. *** This bug has been marked as a duplicate of 16761 ***
