Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366933 - [xbase][generator] Generator cannot be skipped
Summary: [xbase][generator] Generator cannot be skipped
Status: CLOSED INVALID
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.4.3   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-16 06:38 EST by Jan Koehnlein CLA
Modified: 2017-11-10 11:19 EST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Koehnlein CLA 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 CLA 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 CLA 2016-08-15 08:38:28 EDT 
@Karsten there is already org.eclipse.xtext.generator.IGenerator.NullGenerator
Comment 3 Karsten Thoms CLA 2016-08-15 09:24:36 EDT 
#-)
Comment 4 Christian Dietrich CLA 2017-11-10 11:19:40 EST 
binding now comes from DefaultXbaseRuntimeModule thus irrelevant