| Summary: | UnsupportedOperation setting forward reference | ||
|---|---|---|---|
| Product: | [Modeling] MDT.UML2 | Reporter: | Ed Willink <ed> |
| Component: | Core | Assignee: | Kenn Hussey <Kenn.Hussey> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.0.0 | ||
| Target Milestone: | M3 | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
|
Description
Ed Willink
You shouldn't need to make any changes to the content of this resource in order to open it. I'm currently working on XMI interchange support and should have a build available with the changes by Monday. (In reply to comment #1) > I'm currently working on XMI interchange support I'm not sure what that means to me. I'm having a fairly torrid time trying to get the UML-derived pivot model to regenerate from a UML 2.4 Infrastructure model. Am I trying too soon, or am I providing useful feedback? You're trying too soon. :) Support for UML 2.4 in UML2 is scheduled for completion by M4. I'm progressing in a stepwise fashion. Step 1 was for the API and tooling to be based on the new metamodel. Step 2 (currently in progress) is to add support for "external" resources, which includes a) automatic migration of "legacy" UML2 resources, b) interchange of UML resources (in XMI format) base on the official OMG format, and c) interchange of CMOF 2.4 resources. I'll have these essentially complete by this coming Monday. This is related to the issues reported in bug 359964, which have now been fixed. The fix is available in the latest UML2 4.0 integration build. (In reply to comment #5) > The fix is available in the latest UML2 4.0 integration build. Build is a bit hard to consume since it imposes a 3.8 lower bound on org.eclipse.core.runtime that is not present in M2. Similar UOE remained but cleared up once I used CMOF202UMLResource rather than CMOF2UMLResource. No idea what the difference is, but all seems ok now. |