| Summary: | JavaValidator isn't registered, if grammer is not generated | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Benjamin Schwertfeger <benjamin.schwertfeger> |
| Component: | Xtext | Assignee: | Jan Koehnlein <jan> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Andreas.Muelder, jan, sebastian.zarnekow, tmf.xtext-inbox |
| Version: | 1.0.0 | Flags: | sebastian.zarnekow:
indigo+
|
| Target Milestone: | M5 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
| Bug Depends on: | 334080 | ||
| Bug Blocks: | |||
|
Description
Benjamin Schwertfeger
This is intentional: We do not register anything for EPackages that are imported because the Xtext grammar is not the primary source for those packages and should not alter their behaviour or semantics. Developers have to do this explicitly. Although this often causes confusion I'm inclined to keep the current behaviour. Hi everybody, I also stumbled upon this "bug". It took me an hour to find out what was wrong. If its not a bug, it should definitely(!!!) be documented. It's not documented in the build-in help. We should only register for EPackages of elements that can be contained, to avoid a giant composite validator for often referenced languages such as Ecore or JvmTypes. If we resolve Bug 334080, we can register the EValidator for all these EPackages, but only in the context of a single language, making it less invasive with regard to other EMF based plug-ins. Implemented and pushed to MASTER. Closing all bugs that were set to RESOLVED before Neon.0 Closing all bugs that were set to RESOLVED before Neon.0 |