Community
Participate
Working Groups
Build Identifier: 20100617-1415 This leaves the project in question in an inconsistant state and detached from CVS. In addition there is a stack trace in the logs. This also fails in RAD 7.5.5.1 using eclipse 3.4.2 and I also downloaded 3.5.2. All give the same error. This feature used to work in RAD 7.0.0.7 which used an eclipse 2.x build. !ENTRY org.eclipse.jst.j2ee 4 0 2010-07-28 11:23:01.176 !MESSAGE !STACK 0 java.lang.NullPointerException at org.eclipse.jst.j2ee.project.EarUtilities.getReferencingEARProjects(EarUtilities.java:193) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:318) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:308) at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:151) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:120) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:426) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:302) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:286) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:327) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:312) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Reproducible: Always Steps to Reproduce: In our case we import 200+ projects 1. Import head of all projects into empty workspace. 2. Import a full psf of those projects (tagged). Somehwere during the process it will fail with error deleting resource. 3.view the workspace and you will notice one of the projects are detached from CVS in an inconsistant state.
Created attachment 175734 [details] PSF that fails In addition these projects are setup in cvs repo as seperate modules of the cvsroot.
*** This bug has been marked as a duplicate of bug 301223 ***
Was there any further information in the log in this case? It would be interesting to know what file it failed to delete, to see if there is a pattern here. The usual cause of this error is that some thread or process has an open file handle that is preventing the deletion.
Fails on different files. Sometimes it fails on the first few projects and sometimes it fails 5-10 minutes down the road. No pattern that I can see. PC
The stack trace given in comment 0 is not correct for this bug. Correct stack traces and screen shots are attached to bug 301223.