| Summary: | [console] No duplicates violation saving an OCL Interpreter constraint | ||
|---|---|---|---|
| Product: | [Modeling] OCL | Reporter: | Ed Willink <ed> |
| Component: | Core | Assignee: | OCL Inbox <mdt-ocl-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | felix.dorner, nicolas.f.rouquette |
| Version: | 1.3.0 | Keywords: | plan |
| Target Milestone: | --- | Flags: | ed:
indigo-
|
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | Usability | ||
| Bug Depends on: | |||
| Bug Blocks: | 318358 | ||
|
Description
Ed Willink
I can still reproduce this in org.eclipse.ocl.examples.interpreter 3.0.2. If I remove line 135, res.setOCLExpression(parsed), as Ed suggests in the newsgroup, the error disappears. I am afraid that: the relevant code is only examples it is being superseded by the Xtext OCL Console the tentative fixes don't look very convincing some of the tentative fixes may affect the core code (The new code uses ExpressionInOCL as the query quantum, so there is no problem with orphan self variables.) So: WONTFIX Ok thanks. *** Bug 409668 has been marked as a duplicate of this bug. *** CLOSED after more than a year in RESOLVED state. and CLOSE |