mdt-uml2.dev

Hi
The Juno release of MDT/UML2 adds UML 2.4 and 2.4.1 support and 
consequently many more namespaces whose content handlers need to be 
correctly registered.
When running within Eclipse, the magic of extension points should ensure 
that this happens automatically.
When running standalone, these registrations have been a consumer 
responsibility. Most modeling tools have emerged in the last few years 
while UML2 has been stable with support for UML 2.2 and so the 
complexities of multi-version support is easily overlooked in some 
handcrafted UML initialisation code.
In the latest MDT/UML2 I-build, there is a UML standalone initialization 
routine (https://bugs.eclipse.org/bugs/show_bug.cgi?id=364419). Just 
invoke UMLResourcesUtil.init(null). This does all the hard work, and 
should hide the next generation of changes for UML 2.5. Only the 
physical location URI mappings are missing; i.e. from the resolution of 
"platform:/resource/org.eclipse.uml2.uml.resources/profiles/" to 
URI.createURI(UMLResource.PROFILES_PATHMAP); similarly for 'metamodels' 
and 'libraries'. If you have automated plugin location, using classpath 
analysis as performed by MWE2's StandaloneSetup scanPath, or 
org.eclipse.ocl.examples.domain.utilities.StandaloneProjectMap, this 
missing step may be done automatically as well.
A patch to upgrade org.eclipse.ocl.uml.OCL.initialize(resourceSet) to 
call UMLResourcesUtil.init(resourceSet) is in the pipeline, so consumers 
of OCL.initialize need take no action other than taking the opportunity 
to remove their duplicate initializations.
Other tools are encouraged to start using UMLResourcesUtil.init(null) as 
soon as possible so that any residual bugs are fixed for Juno, ensuring 
that UML 2.5 can be introduced without a further downstream 
initialization ripple.
    Regards
        Ed Willink
_______________________________________________
mdt-uml2.dev mailing list
mdt-uml2.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-uml2.dev

Hi Kenn
I'm trying to make Complete OCL validation work interactively.
i.e.
User has Ecore/UML/... meta-model
User has Complete OCL complement to that meta-model
User has instance of that meta-model
then
User validates and the Complete OCL invariants are executed
Problem has always been that validation does not know that Complete OCL 
exists so it is ignored and useless.
Solution: provide a Load Complete OCL Menu Action to enhance the model 
and/or ResourceSet and/or EValidatorRegistry.
This can be applied at M1 or M2, so if a Complete OCL document is loaded 
into an Ecore editor, the additional constraints can enforce arbitrary 
style constraints such as "interface-name must start with I".
So if Complete OCL can augment the UML Model Editor externally at M2, 
shouldn't Stereotypes also provide OCL that works internally at M2? I 
see Papyrus traffic that seems to be wanting this.
Since MDT/UML2 has no dependencies on MDT/OCL this capability is not 
directly supported by MDT/UML2, but is there some form of delegate 
already in place that MDT/OCL should be exploiting or is something new 
required?
	Regards
		Ed Willink
Hi Kenn

There will be no more API changes.

That's good, I feared that UML 2.4 enhancements might have a new 
excitement every milestone till M6.

If you have any notes on what you had to do to adopt the new version 
(other than the things you just mentioned), I'll be sure to include 
that in my migration guide...

I'm adding notes to http://wiki.eclipse.org/MDT/OCL/FAQ#UML_2.4_migration.
    Regards
        Ed
Hi
Are there any detailed plans for what will be in UML2 4.0.0 (the 
official project plan seems to be all boilerplate)?
The 4.0.0M2 release shows some interesting UML 2.4 progress, but hits 
MDT/OCL.
Some problems whereby MDT/OCL extends the MDT/UML2 meta-model are 
unavoidable, but others are less obvious.
In particular JUnit tests fail until
the UML URI is changed to 4.0.0 in test models; is a migration 
capability planned or have we got our declarations wrong?
the UML package name is changed from "uml" to "UML"; probably a 
necessary UML-alignment change
PrimitiveTypes package names are sorted out; probably a necessary 
UML-alignment change
    Regards
        Ed Willink
James, Kenn,
Projects are required to keep meta data up to date using the MyFoundation
Portal (http://portal.eclipse.org/).  The following problems were found
with this project's meta-data:

* The date for release "3.2.0" is in the past, but the release is not
marked as completed. If it is completed, it should be marked as completed;
if it has been postponed, it should be given a new target date.
* There is no next/future release of this project. All Eclipse projects
must have a "next release" planned and scheduled.

mdt-uml2.dev

[mdt-uml2.dev] UML Standalone Initialization

Re: [mdt-uml2.dev] Complete OCL validation at M1 and M2

Re: [mdt-uml2.dev] Complete OCL validation at M1 and M2

[mdt-uml2.dev] Complete OCL validation at M1 and M2

Re: [mdt-uml2.dev] UML 2.4 plans

Re: [mdt-uml2.dev] UML 2.4 plans

[mdt-uml2.dev] UML 2.4 plans

[mdt-uml2.dev] Project meta data is out of date for modeling.mdt.uml2

Re: [mdt-uml2.dev] Fwd: [mdt.dev] MDT UML2 3.2.0 Indigo Release Review Material

[mdt-uml2.dev] Fwd: [mdt.dev] MDT UML2 3.2.0 Indigo Release Review Material