Community
Participate
Working Groups
The org.eclipse.ocl.uml.OCL.initialize functionality is inappropriate for the new UML 2.4.1 URIs. This gives almost 100% failures to run.
I thought this might be easy given that I'd already been tackling this for Pivot UML support. It doesn't seem to be; the existing half-baked initialization interacts badly with the fuller pivot init. A single clean user-consumable standalone init is needed. Hopefully MDT/UML2 will provide one which we can re-use and/or extend. Until then, I'm not inclined to hack the current approach. Therefore all UML standalone JUnit tests are retracted from the build. The plugin JUnit tests still run so at least most functionality remains tested. This has no immediate impact on users, expect any user who hoped that OCL.initialize would enable UML2 to be used will be disappointed. UML2 is to all intents and purposes unuseable in standalone at present.
(In reply to comment #1) > Until then, I'm not inclined to hack the current approach. Therefore all UML > standalone JUnit tests are retracted from the build. The plugin JUnit tests > still run so at least most functionality remains tested. But only interactively. Plugin tests still disabled by Bug 358801.
Fixed by an explicit TypesPackage.eINSTANCE before UMLPackage is initialised. UML standalone test re-enabled. Pushed to master. Tests run again.
CLOSED after a year in the RESOLVED state.