Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [modeling-pmc] [mdt-ocl.dev] Hosting OMG OCL specification development at Ecl; ipse

FWIW, I have an external dependency that I'm primary contributor for and that is a dependency for my Eclipse project. It's turned out to be quite a maintenance PITA as you need to do a CQ every time you have a fix that you need to use on the Eclipse side -- even though Eclipse legal is very good about moving things through process, it is not the kind of thing that you're going to want to be doing routinely, which ends up meaning that a) the dependency get's a lot less love or b) you end up maintaing things out of synch. This get's doubly difficult if -- as in my case -- you need to deliver the plugin on both sites.

I'd suggest you keep the dependency at binary/p2 unless you really need source. If you need a dependency on OMG OCL another option is to use the Install Modeling Components mechanism (see e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=304008). When defining it you can put in a reference to the external update site. If that external site mets the Eclipse IP standards you might not even have to have an IP disclaimer but you should check with Cédric and Legal on that.

hth a bit,

Miles

On Dec 7, 2010, at 2:06 AM, Ed Willink wrote:

Hi Kenn, Ed

The 'OMG' plugins would be of two forms.

a) Model definitions, e.g. OCL.uml, OCL24.oclstdlib

b) Specification generation tooling, QVTo, Acceleo scripts.

Today, I and to a lesser extent Adolfo are almost the sole contributing participants to both Eclipse OCL and the OMG OCL RTF, so IP is not a particular problem; the underlying specification already has a CQ.

But you're right that this is a pretty bad idea, for instance if Mariano Belaunde, the RTF chair, needs to contribute as well as review we get faced with the difficult corrolary that Mariano would need to become an Eclipse OCL committer.

I guess I'll have to create another SourceForge project, or perhaps further abuse my UMLX SourceForge project that hosts non-IP approved example plugins.

     Regards

        Ed Willink
 
On 06/12/2010 18:14, Kenn Hussey wrote:
Ed,

Where will the IP for these new projects come from? If anything originates from activities of (members of) the RTF instead of directly from you, you'll need to have a CQ approved before committing those changes (since MDT OCL is a "mature" project and hence does not qualify for the parallel IP process).

Cheers,

Kenn

On Mon, Dec 6, 2010 at 5:24 AM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
Hi

OMG appear to be unable to provide a CM facility for development of its specifications: UML is hosted at modeldriven.org and requests for a repository for OCL have been ignored.

My OMG RTF activities that make the OCL specification model-generated require a CM repository, so I would like to host some org.omg.ocl... plugins at cvsroot/modeling org.eclipse.mdt/org.eclipse.ocl/omg/... (migrating to GIT post Indigo).

As well as providing a host for OMG, it will also clearly distinguish the 'Eclipse-independent' OMG OCL plugins from the added-value Eclipse OCL plugins while allowing Eclipse OCL to layer on top of the OMG plugins.

Is this within project scope and acceptable?

   Regards

       Ed Willink



_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev


_______________________________________________
mdt-ocl.dev mailing list
mdt-ocl.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-ocl.dev


No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1170 / Virus Database: 426/3300 - Release Date: 12/06/10

_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc

Back to the top