| Re: [cross-project-issues-dev] Fwd: [modeling-pmc] Ed Willink standing down from MMT, OCL, QVTd, QVTo |
Thanks. Yes, I was already looking at EMF Services' dependencies:
I don't there there is an urgent need to remove OCL, but if no one steps up ever, then there will be a need eventually, and it's best to take action before it's urgent.
Le 03/04/2024 à 17:04, Ed Merks via cross-project-issues-dev a écrit :
For EMF Services, OCL is used in EMF Validation in a single optional bundle [1] and an example project [2]. EMF Transaction does not depend on it (except indirectly as it depends on EMF Validation). This could be moved out of what's contributed to the SimRel if necessary.FYI,
Unless someone steps up to maintain these projects and their contributions, the train will badly impacted.
The yellow projects below directly downstream via requirement dependencies on OCL:
While it's not part of what we ship in the SimRel, Sirius has a dependency on OCL [3], but AFAIK this is very rarely used, if ever. We already thought about dropping this.
If these two dependencies were removed (especially the EMF Validation one), this would also clear GMF Runtime, Ecore Tools, EEF and EMF Compare (not 100% sure for the last two). AFAICT they all only appear because of transitive dependencies to EMF Validation.
[1] https://github.com/eclipse-emfservices/emf-validation/tree/master/bundles/org.eclipse.emf.validation.ocl
[2] https://github.com/eclipse-emfservices/emf-validation/tree/master/examples/org.eclipse.emf.validation.examples.ocl
[3] https://github.com/eclipse-sirius/sirius-desktop/tree/master/plugins/org.eclipse.sirius.common.ocl
The following are transitively downstream:
-------- Forwarded Message --------
Subject: [modeling-pmc] Ed Willink standing down from MMT, OCL, QVTd, QVTo Date: Mon, 18 Mar 2024 14:27:09 +0000 From: Edward Willink via modeling-pmc <modeling-pmc@xxxxxxxxxxx> Reply-To: PMC members mailing list <modeling-pmc@xxxxxxxxxxx> To: emo@xxxxxxxxxxx, modeling-pmc@xxxxxxxxxxx CC: Edward Willink <ed@xxxxxxxxxxxxx>
Hi
Further to my comment on https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4418 please do whatever is necessary to accommodate my non-participation in ongoing support for MMT, OCL, QVTd, QVTo.
I regret that I no longer have the necessary enthusaism to chase the incessant infrastructure changes inflicted by the EF without any consideration for supporting unfunded projects. The recent changes seem to me ill-considered and detrimental. I get no satisfaction from degrading my projects and can hardly be expected to do so in my own time. Sadly the complexity of some bad historical decisions regarding project containerisation result in flawed webmaster actions that just seem to provoke endless rows and half actions in attempting to resolve them. My attempts to help seem to just result in stress all round.
I hope that some way can be found to keep OCL and QVTd going. (QVTo still has a project lead but no releng.)
I propose to keep a foot in the door with MoDisco and provide solutions to some of the inter-project chasms that Polarsys does not seem to have resolved.
- sample reflective graphical model editor
- model type hierarchy view (Ecore/UML/Pivot/... rather than just Java)
- 'EMF' model search
Regards
Ed Willink
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/modeling-pmc
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
