[releng] OCL.uml references UML2 2.1.0 not 3.0.0

[eclipse-ocl-bot]

| --- | --- | | Bugzilla Link | 282700 | | Status | CLOSED FIXED | | Importance | P3 minor | | Reported | Jul 07, 2009 11:33 EDT | | Modified | May 29, 2012 13:23 EDT | | Version | 1.3.0 | | Reporter | Ed Willink |

Description

Attempting to load OCL.uml via a getResource() and a pathmap (pathmaps need adding) fails because the reference is to http://www.eclipse.org/uml2/2.1.0/UML\ rather than http://www.eclipse.org/uml2/3.0.0/UML.

Workaround is to change to 3.0.0; probably needs something similar\ in OCL.ecore.

Underlying bug is?

Did UML fail to declare a synonym to allow 2.1.0 to be used?\ Is EMF incorrectly loading an Ecore resolution of 2.1.0?\ Should EMF automatically correct the Ecore for UML content references?

[This problem was revealed by trying to get the BasicOCLTest.test_enumerationLiteralValue_198945 JUnit test working on the UML binding.]

[eclipse-ocl-bot]

By Alexander Igdalov on Dec 22, 2009 06:04

Hi Ed,

As I see it, links to 2.1.0 have been changed to 3.0.0 in OCL.uml. Can we close this issue?

Cheers,

• Alex.

[eclipse-ocl-bot]

By Ed Willink on Dec 22, 2009 07:09

Hmm. It looks like my edit to add TemplateParameterType picked up the new reference. So perhaps UML2 has an auto-migration mechanism, which is very good now, but wasn't when I reported the problem.

I think we should try to understand what went wrong, how it went right, and try to ensure that we offer migration to our clients.

Change to minor.

[eclipse-ocl-bot]

By Ed Willink on Jun 26, 2010 11:38

If we have a residual bug it's probably in code heading for deprecation via the pivot model.

[eclipse-ocl-bot]

By Ed Willink on May 29, 2012 13:23

Closing all bugs resolved in Indigo.