EMF Validation 1.14.2rc2 & EMF Transaction 1.14.3rc1

[pcdavid]

Signed-off-by: Pierre-Charles David pierre-charles.david@obeo.fr

[merks]

@pcdavid

It would be awfully nice if this issue were addressed:

#1288 (comment)

It's really a trivial fix...

[pcdavid]

It's not clear to me what must be done. The issue seems to talk about indexes, Lucene and <index path="index"/> that should be removed. I don't see any mention of such an <index> element in either EMF Validation or EMF Transation (here, here and here.

On the table in this comment, the lines for EMF Validation & Transaction are striked, so I interepreted that as "these do not declare an index, there is nothing to do".

[merks]

These are points of confusion:

• https://github.com/eclipse-emfservices/emf-transaction/blob/e662e04b1e6805c6c7f7f694424b20a6be7edf37/doc/org.eclipse.emf.transaction.doc/plugin.xml#L10
• https://github.com/eclipse-emfservices/emf-transaction/blob/e662e04b1e6805c6c7f7f694424b20a6be7edf37/doc/org.eclipse.emf.workspace.doc/plugin.xml#L14

The analyzer only does a pattern match, not considering you might have commented out useless content.

These are actual errors logged when one opens the help (which I see whenever I test the modeling package for each M*/RC*):

Things missing from the build.properties?

You should be able to reproduce this with a self-hosted launch from your development IDE.

[pcdavid]

The documentation issues should be fixed by eclipse-emfservices/emf-validation#66 and eclipse-emfservices/emf-transaction#45.

I also want to remove source features (eclipse-emfservices/emf-validation#21 and eclipse-emfservices/emf-transaction#33) before making a (hopefully final) contribution for 2026-06.

[merks]

@pcdavid

You're awesome! I really, really appreciate that. ❣️

I would have helped more directly, but there is no Oomph setup so I would have been tempted to create that first. For MWE it took me 5 minutes to materialize a development IDE with the setup, fix the problem, and push a PR. Just saying. 🙊

[pcdavid]

See #1361

As for Oomph, sorry, I'm sure for someone who already knows Oomph it's more efficient.
But I spend most of my time on web-related projects now and I don't have the time/energy to adopt completely new (for me) tools and workflows for these RCP projects in maintenance mode.