Community
Participate
Working Groups
Build id: I20070320-0010 Import the to_be_attached project. - autobuild in on Observe only one expected error in the problems view: But I don't like spam Perform a clean for this project. --> now you have 3 errors, and an exception in the console (I'll attach the stack trace) a way to get rid of the 2 unexpected errors: suppress the 2 import lines: import echo.Echo; import gen.AGen; Save your changes. Then, perform a Crtl + Shift + O --> only one import is added, whereas we expect the 2 lines to be added. Save your changes and perform a second Crtl + Shift + O Errors are cleared.
Created attachment 61564 [details] Test project
stack trace !ENTRY org.eclipse.jdt.apt.core 4 1 2007-03-21 16:07:02.547 !MESSAGE Unable to commit new contents for working copy AGen.java !STACK 1 Java Model Exception: Java Model Status [Invalid resource: null] at org.eclipse.jdt.internal.core.CompilationUnit.updateTimeStamp(CompilationUnit.java:1246) at org.eclipse.jdt.internal.core.CommitWorkingCopyOperation.executeOperation(CommitWorkingCo pyOperation.java:164) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:720) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:784 ) at org.eclipse.jdt.internal.core.CompilationUnit.commitWorkingCopy(CompilationUnit.java:354) at org.eclipse.jdt.apt.core.internal.generatedfile.CompilationUnitHelper.commitNewContents(C ompilationUnitHelper.java:41) at org.eclipse.jdt.apt.core.internal.generatedfile.GeneratedFileManager.saveCompilationUnit( GeneratedFileManager.java:1447) at org.eclipse.jdt.apt.core.internal.generatedfile.GeneratedFileManager.generateFileDuringBu ild(GeneratedFileManager.java:518) at org.eclipse.jdt.apt.core.internal.env.JavaSourceFilePrintWriter.close(JavaSourceFilePrint Writer.java:63) at echo.proc.EchoProc.createSourceFile(EchoProc.java:94) at echo.proc.EchoProc.process(EchoProc.java:69) at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.dispatchToFileBasedProcessor(APTDis patchRunnable.java:572) at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.runAPTInFileBasedMode(APTDispatchRu nnable.java:302) at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.build(APTDispatchRunnable.java:598) at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.access$1(APTDispatchRunnable.java:5 90) at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable$1.run(APTDispatchRunnable.java:255) at org.eclipse.jdt.apt.core.internal.env.BuildEnv$CallbackRequestor.acceptBinding(BuildEnv.j ava:611) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:758 ) at org.eclipse.jdt.core.dom.CompilationUnitResolver.resolve(CompilationUnitResolver.java:473 ) at org.eclipse.jdt.core.dom.ASTParser.createASTs(ASTParser.java:731) at org.eclipse.jdt.apt.core.internal.env.BaseProcessorEnv.createASTs(BaseProcessorEnv.java:8 18) at org.eclipse.jdt.apt.core.internal.env.BuildEnv.createASTs(BuildEnv.java:356) at org.eclipse.jdt.apt.core.internal.env.AbstractCompilationEnv.newBuildEnv(AbstractCompilat ionEnv.java:92) at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.build(APTDispatchRunnable.java:261) at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.run(APTDispatchRunnable.java:207) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) at org.eclipse.jdt.apt.core.internal.APTDispatchRunnable.runAPTDuringBuild(APTDispatchRunnab le.java:134) at org.eclipse.jdt.apt.core.internal.AptCompilationParticipant.processAnnotations(AptCompila tionParticipant.java:157) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.processAnnotations(AbstractIma geBuilder.java:590) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.j ava:330) at org.eclipse.jdt.internal.core.builder.BatchImageBuilder.build(BatchImageBuilder.java:59) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildAll(JavaBuilder.java:254) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:172) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:163) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:248) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:251) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:307) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:339) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:137) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58) !SUBENTRY 1 org.eclipse.jdt.core 4 995 2007-03-21 16:07:02.547 !MESSAGE Invalid resource: null
This should be fixed as of I20070321-0800 build. The eventual fix will probably be improved from what is there now, but I believe the 0800 workaround is solid; please let me know if you are still seeing this in 0800. *** This bug has been marked as a duplicate of bug 177962 ***
verified for 3.3 M6 using build I20070321-1800
(In reply to comment #4) Now that the problem is fixed, you can encounter the same behavior as the one described in bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=175794
