| Summary: | regression with unordered groups | ||
|---|---|---|---|
| Product: | [Modeling] TMF | Reporter: | Moritz Eysholdt <moritz.eysholdt> |
| Component: | Xtext | Assignee: | Project Inbox <tmf.xtext-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sebastian.zarnekow |
| Version: | 2.0.0 | Flags: | sebastian.zarnekow:
indigo+
|
| Target Milestone: | SR1 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
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 |
the rule --- DAlarmIndication: description=DESC? ("<" annotations+=DAnnotation+ ">")? status=DStatus? severity=DSeverity "alarm" name=ID ("implements" superAlarm=[DAlarmIndication|FQN])? "{" (("format" format=STRING)? & ("probableCauseFormat" probableCauseFormat=STRING)? & ("recommendedAction" recommendedAction=[DAction|FQN])? & ("correlatedAlarm" correlated+=[DAlarmIndication|FQN])*) attributes+=DEventAttribute* "}"; --- lets antlr raise the following warning "Decision can match input such as "'correlatedAlarm' RULE_ID" using multiple alternatives: 1, 2". Interestingly, this warning only shows up for contentassist-parser, but not for the runtime-parser. This is a regression since it has been working flawlessly with Xtext 1.0.2 Workaround: enable backtracking for XtextAntlrUiGeneratorFragment. I thought I already saw a bug report for this issue, but I can't find it anymore.