Skip to content

fix: stop the workflows from generating Xtend inferrer stubs - #1644

Open
joaodinissf wants to merge 1 commit into
masterfrom
fix/no-xtend-inferrer-stubs
Open

joaodinissf wants to merge 1 commit into
masterfrom
fix/no-xtend-inferrer-stubs

Conversation

@joaodinissf

Copy link
Copy Markdown
Collaborator

Stops the MWE2 workflows from writing an .xtend JVM model inferrer stub next to the Java inferrers of the Check, Check Configuration, Export, Expression, Format and Scope languages.

The change

  • Workflows: generateXtendInferrer = false on the Xbase generator fragment in CommonXbase.mwe2 (Check and Check Configuration), GenerateExport.mwe2, GenerateExpression.mwe2 and GenerateScope.mwe2. GenerateFormat.mwe2 uses StandardLanguage, so the flag goes in its xbaseSupport block.
  • Runtime modules: the flag also stops XbaseGeneratorFragment2 from binding the inferrer in the generated Abstract*RuntimeModule. Each hand-written *RuntimeModule now has an explicit bindIJvmModelInferrer(), and the generated binding is removed from src-gen as the workflows now produce it.
  • checkcfg.core, xtext.export, xtext.expression, xtext.format and xtext.scope get a micro version bump.

The test language in check.test.runtime is not an Xbase language, so its fragment generates nothing and is left unchanged.

Testing

  • Regeneration: after running the six workflows, no .xtend inferrer or xtend-gen folder appears, and the only change in the generated runtime modules is the removed binding.
  • Maven on this branch, with Temurin 21: clean verify with checkstyle:check, pmd:check, pmd:cpd-check and spotbugs:check passes, including the version baseline check. 490 tests ran with no failures or errors, and 2 were skipped.

🤖 Generated with Claude Code

The JVM model inferrers of the Check, Check Configuration, Export,
Expression, Format and Scope languages are Java classes now, but the
Xbase generator fragment still defaulted to generateXtendInferrer, so
every regeneration wrote an .xtend inferrer stub next to the Java one.

Set generateXtendInferrer = false in each workflow. The flag also drops
the bindIJvmModelInferrer binding from the generated runtime modules, so
each hand-written runtime module now binds its inferrer explicitly.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant