Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338551

Summary:	building through eclipse gives error NullPointerException for Plug-in Manifest Builder
Product:	[Eclipse Project] PDE	Reporter:	Lynn Johnson <lynnj>
Component:	UI	Assignee:	Curtis Windatt <curtis.windatt.public>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	3.7
Target Milestone:	3.7 M7
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Lynn Johnson

2011-03-01 11:07:26 EST

Build Identifier: 20100917-0705

When compiling/building a file in eclipse I constantly (but not always) get the error "Building workspace has encountered a problem" "Errors running builder 'Plug-in Manifest Builder' on project lynnj..." java.lan.NullPointerException.  Note that building through ant always works - no problems, no errors.  So I ignore the eclipse errors, but they nag at me.  

From the .log file, the stack back is as follows:
!ENTRY org.eclipse.core.resources 4 75 2011-03-01 08:39:40.549
!MESSAGE Errors occurred during the build.
!SUBENTRY 1 org.eclipse.pde.core 4 75 2011-03-01 08:39:40.549
!MESSAGE Errors running builder 'Plug-in Manifest Builder' on project 'lynnj_mldpBldCache6.2'.
!STACK 0
java.lang.NullPointerException
	at org.eclipse.pde.internal.core.builders.SourceEntryErrorReporter.validate(SourceEntryErrorReporter.java:426)
	at org.eclipse.pde.internal.core.builders.BuildErrorReporter.validateBuild(BuildErrorReporter.java:233)
	at org.eclipse.pde.internal.core.builders.BuildErrorReporter.validate(BuildErrorReporter.java:139)
	at org.eclipse.pde.internal.core.builders.ErrorReporter.validateContent(ErrorReporter.java:127)
	at org.eclipse.pde.internal.core.builders.ManifestConsistencyChecker.validateBuildProperties(ManifestConsistencyChecker.java:316)
	at org.eclipse.pde.internal.core.builders.ManifestConsistencyChecker.validateProject(ManifestConsistencyChecker.java:231)
	at org.eclipse.pde.internal.core.builders.ManifestConsistencyChecker.build(ManifestConsistencyChecker.java:157)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Thanks - Lynn

Reproducible: Sometimes

Steps to Reproduce:
1. Make a change to a java file
2. save the file
3. get the error
4. Run build.xml - ant build - there is no error

Comment 1 Curtis Windatt

2011-03-01 13:33:00 EST

We will try to investigate in M7.  It appears that the plug-in registry doesn't have a model for the project being built.

Comment 2 Curtis Windatt

2011-03-14 17:07:12 EDT

Added an NPE check.  If we don't have a model for the project being looked at, we will skip over reporting errors for missing library output.  See SourceEntryErrorReporter.java.