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

Bug 366933

Summary:	[xbase][generator] Generator cannot be skipped
Product:	[Modeling] TMF	Reporter:	Jan Koehnlein <jan>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	CLOSED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	btickets, christian.dietrich.opensource, karsten.thoms, sven.efftinge
Version:	2.4.3
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Jan Koehnlein

2011-12-16 06:38:04 EST

Commenting out the GeneratorFragment in the MWE workflow does not have an effect, as the XbaseGeneratorFragment contributes an IGenerator in any case. This is not very suggestive.

Workaround: bind a dummy IGenerator.

Comment 1 Karsten Thoms

2016-08-15 08:33:12 EDT

@Jan: So what is the action here? Shall the XbaseGeneratorFragment(2) get an option that would bind IGenerator to an empty impl? Should a NullImpl be added to the IGenerator interface as default impl?

Comment 2 Christian Dietrich

2016-08-15 08:38:28 EDT

@Karsten there is already org.eclipse.xtext.generator.IGenerator.NullGenerator

Comment 3 Karsten Thoms

2016-08-15 09:24:36 EDT

#-)

Comment 4 Christian Dietrich

2017-11-10 11:19:40 EST

binding now comes from DefaultXbaseRuntimeModule thus irrelevant