Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323256 - NPE in Builder when starting with an empty Workspace/Project
Summary: NPE in Builder when starting with an empty Workspace/Project
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 1.0.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-20 10:41 EDT by Lothar Wendehals CLA
Modified: 2017-10-31 11:26 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lothar Wendehals CLA 2010-08-20 10:41:29 EDT
Build Identifier: Helios

When starting my RCP application with an empty workspace, I first create a project with Xtext nature and XtextBuilder like this:

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>Configurations</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.xtext.ui.shared.xtextBuilder</name>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.xtext.ui.shared.xtextNature</nature>
	</natures>
</projectDescription>

When creating the first DSL files, the builder crashes with the following NPE:
java.lang.NullPointerException
	at org.eclipse.xtext.ui.guice.AbstractGuiceAwareExecutableExtensionFactory.create(AbstractGuiceAwareExecutableExtensionFactory.java:50)
	at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:262)
	at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
	at org.eclipse.core.internal.events.BuildManager.instantiateBuilder(BuildManager.java:784)
	at org.eclipse.core.internal.events.BuildManager.initializeBuilder(BuildManager.java:737)
	at org.eclipse.core.internal.events.BuildManager.getBuilder(BuildManager.java:482)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
	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)


Reproducible: Always
Comment 1 Sebastian Zarnekow CLA 2010-10-05 09:13:49 EDT
see also bug 289212
Comment 2 Sven Efftinge CLA 2012-11-14 05:22:32 EST
I think this has been fixed. Please reopen if I'm wrong.
Comment 3 Eclipse Webmaster CLA 2017-10-31 11:26:15 EDT
Requested via bug 522520.

-M.