| Summary: | Operation bodies included in documentation | ||
|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Kenn Hussey <Kenn.Hussey> |
| Component: | Core | Assignee: | Kenn Hussey <Kenn.Hussey> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Flags: | Kenn.Hussey:
indigo+
|
| Version: | 3.1.0 | ||
| Target Milestone: | RC1 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
The fix has been committed to CVS. The fix is available in the RC1 build. Closing for Indigo release. |
The contents of body expressions are included in operation documentation even if/when the option to process operation bodies is chosen in the UML import wizard. Inspection of the source code uncovered a Boolean expression which references an intended constant: if (specification != null && !(eModelElement instanceof EOperation && options != null && OPTION__PROCESS.equals(options.get(OPERATION_BODY)))) { addDocumentation(eModelElement, specification.stringValue()); } The OPTION__OPERATION_BODIES constant should clearly be referenced here instead of OPERATION_BODY.