Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mdt.dev] Re: MDT/OCL Text Editor and EMFT Model Registry suggestion 
Hi, Ed,
Obviously, I support these refactorings: an OCL editor is a major small-c component missing from MDT and a shared model registry is valuable to the entire spectrum of modeling tools offered by Eclipse. 

Some questions for Ed W.:
Does the EMFT Model Registry component propose to release with Galileo? It's too late to "officially" join the train, but that may not be critical. Will it be incubating in this release? Or, would it be ready to graduate in Galileo time? Will it want more validation by other projects than QVT and UMLX before graduating? What do you know of IMP's plans concerning releasing/graduation? They don't have a project plan posted ... Does the editor require run-time components from IMP, or is IMP strictly a development-time tooling dependency? 

Some questions for the Modeling PMC:
The Declarative QVT project is, as I understand it, currently in incubation. OCL is not. To what extent can a non-incubating component like OCL that is on the train have dependencies on incubating projects? Could OCL require an incubation release of a dependency (0.x.0)? Obviously, the dependent project would have to have produced at least a formal release, even in incubation.
What work-arounds might there be? Could OCL provide an "example" that requires incubation and/or non-released dependencies? I suppose that, in the end, it would probably be best to target a post-Galileo release of the editor? 

Thanks,

Christian

On 1-Feb-09, at 4:44 AM, Ed Willink wrote:


Hi All

In https://bugs.eclipse.org/bugs/show_bug.cgi?id=261742 #2
Christian Damus revealed that we are discussing migrating
the (currently M2M/QVT Declarative) OCL Editor to MDT/OCL.

This incurs two dependency problems.

The text editor uses IMP, which is an incubation project,
so the additional optional MDT/OCL editor plugins might
have API stability issues. IMP has hopefully only very
minor IP issues.

The semantic validation of OCL requires a solution to the
problem of where is the (potentially user-defined non-plugin)
package named Xyzzy? The (currently M2M/QVT Declarative)
Model Registry solves this problem. The Model Registry
was originally part of UMLX, it has moved to QVT Declarative.
A further move of generic modeling functionality to MDT/OCL
does not seem right. Therefore a new EMFT project seems more
appropriate.

Kenn, Ed, Rich, Frederic, Jean, ...  Please advise on how best
to proceed with a fairly small EMFT Model Registry project.

All: Please be aware of the plans and please comment, especially
if you have ideas or available resources for further Model Registry development. 

Please respond on mdt.dev only.

Attached PDF provides more background on the project dependencies.

  Regards

      Ed Willink
<ModelRegistry.pdf>_______________________________________________
mdt.dev mailing list
mdt.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt.dev


--
Christian W. Damus
Senior Software Developer, Zeligsoft Inc.
Component Lead, Eclipse MDT OCL and EMF-QTV
E-mail: cdamus@xxxxxxxxxxxxx

Back to the top